Ryan's Journal

If you're developing for Firefox 2.x and you get an error "aWindow.document.documentElement has no properties" from the internal session management scripts (nsSession.js line 400), check that all of the files you reference exist, from the stylesheets to the string bundles. It is not a deterministic error; after discovering a solution, I thought at first the behavior I saw was being 'resolved' by per-session caching of an internal not-found state for chrome URIs, but it doesn't just come up the first time a missing file is encountered, nor does it always come up the first time. Or maybe that is the root cause of the intermittent symptoms and there's a timeout factor involved; I'm not sure.

There's very little documentation on this specific warning, so I thought I'd throw it out there. Don't just make placeholders for files you plan on creating in your XUL pages, touch or otherwise create those files as well.

You must login to leave a comment