At a minimum, we should be bumping the version number on the Javascript. It's been at "m7"!?! for ages. I'll look at fixing that now. It doesn't help people moving from one snapshot to the next, but the theory is that 95% of people move from one released version to the next, and if you're on a snapshot, you have some extra headaches.
-- Adam On 6/12/07, Danny Robinson <[EMAIL PROTECTED]> wrote:
We recently made some updates to the core javascript library in Trinidad. These changes caused some headaches for users having to clear their browser caches etc, so the updates were not seamless. Should we use a similar unique id mechanism that was introduced for the skins css files, so that changes cause a new filename to be generated, and hence causing the browser to reload? Is this feasible/possible? Danny -- Chordiant Software Inc. www.chordiant.com
