As discussed in #mozilla <dveditz> mikep: but you should definitely call refreshPlugins in your install script <mikep> OK, can I remove DELAYED_CHROME then? <dveditz> hm <mikep> I remember having a hard time without that in there. <dveditz> mikep: then you'd better leave that in :-( <dveditz> mikep: if they were already running calendar then the calendar xul is cached and you'll have problems <dveditz> mikep: I guess the installer needs a way to flush the xul cache if any chrome is registered <mikep> dveditz: You mean without the delayed chrome? <dveditz> mikep: yeah <dveditz> mikep: and not just the calendar xul, the browser xul that you're trying to overlay (presumably) with a task menu entry
Fastload (both JS and XUL) probably screw this up, too. I believe those only check whether they need rebuilding at startup, we'd have to invent a way to mark those obsolete too.
I have been able to get around this bug by disabling the xul cache preference nglayout.debug.disable_xul_cache. Ideally the xul cache file xul.mfasl should be cleared when the page cache is cleared in the UI by the user. This bug is kind of old but I just got burned by it when we were sending out an upgraded XUL application to a client. They kept seeing the old application until I had them manually remove xul.mfasl and restart Mozilla. We later ended up slapping a sticker on each CD reminding customers to remove the xul cache. In the interest of promoting Mozilla/Firebird as an application framework I think this bug should set be as a blocker for 1.6a.
There is no installer anymore on SeaMonkey trunk builds but maybe there are other reasons to allow flushing the XUL cache. Daniel, I've heard you're on holiday till the end of this month. Still working on this? Or has it been fixed elsewhere?
Component: Installer → XP Toolkit/Widgets: XUL
Product: Mozilla Application Suite → Core
QA Contact: ktrina → xptoolkit.xul
OS: Linux → All
Hardware: PC → All
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.