So clearing the session via the Tools menu did not make the issue go
away for me, but restarting the browser WITHOUT restoring the session
seems to have done the trick.

On May 14, 2:58 am, Eric Ongerth <[EMAIL PROTECTED]> wrote:
> I'm busily switching all my page templates from Prototype to jQuery.
> I'm getting the following error I never saw before (seen via Firebug)
> on a page that has been entirely changed over to jQuery, with
> prototype all gone and no longer included/loaded.
>
> [Exception... "Component is not available" nsresult: "0x80040111
> (NS_ERROR_NOT_AVAILABLE)" location: "JS frame ::
> file:///H:/Program%20Files/Mozilla%20Firefox/components/nsSessionStore.js
> :: sss_saveState :: line 1753" data: no]
> [Break on this error] oState.session = { state: ((this._loadState ==
> STATE_RUNNING) ? STATE_RUNNIN...
>
> What could be causing this?  Is it just a Firefox bug?  (FF 2.0.0.14
> on winXP)
>
> I've seen only one "component is not available" error similar to this
> one (though not the identical error) before and it disappeared when I
> fixed a separate javascript error due to some mistake I had made.  But
> this time is not so easy because I have no other errors on this
> particular page that I'm aware of and it is otherwise "working".
>
> Eric

Reply via email to