xul caching

[Pavel Krivanek]

Hi all,

if I've got a simple javascript-only XUL application (that means the
only directory with application.ini, chrome contents with main.xul
containing some scripts etc.). Prefs.js contains this settings:

pref("browser.dom.window.dump.enabled", true);
pref("javascript.options.showInConsole", true);
pref("javascript.options.strict", true);
pref("nglayout.debug.disable_xul_cache", true);
pref("nglayout.debug.disable_xul_fastload", true);

However it still seems that the XUL caching still works because if I
do some change in main.xul, no change takes effect and the only way
how to make it work is to rename the application directory.

Any idea where the problem is?

Cheers,
-- Pavel

[Nickolay Ponomarev]

On Sun, Nov 1, 2009 at 1:09 PM, Pavel Krivanek <pavel.k...@gmail.com>wrote:

> if I've got a simple javascript-only XUL application (that means the
> only directory with application.ini, chrome contents with main.xul
> containing some scripts etc.). Prefs.js contains this settings:
>

> Are you sure it's the right profile? Tried getting the disable_xul_cache
pref from your code to see if it's indeed true?

However it still seems that the XUL caching still works because if I
> do some change in main.xul, no change takes effect and the only way
> how to make it work is to rename the application directory.
>

You don't say if you know how it's supposed to work, so it's not clear if
you misunderstand how it should work or if it indeed doesn't work. Try
specifying more precise steps you take and the results you see?

The expected behavior is: when reloading the document (e.g. by closing and
reopening a window), the updated code is loaded. Do you reopen the main.xul
window?

Nickolay