Errormessage in Firebug: NS_ERROR_XPC_JS_THREW_STRING

[Wolfgang]

From time to time, i hget the following message in Firebug. Unfortunately, i am not able to reproduce it. It shows up on different (Windows) Systems.

[code]
[Exception... "'Die Erlaubnis f

[thejoker101]

I've had that message too, from time to time. Not sure what it means though or what causes it.

[mystix]

me three. doesn't seem to be causing any obvious problems in FF2, Opera 9 or IE6/7 though. wonder if it's just a firebug thing?

[tryanDLS]

Is it possible you're trying to access the document before it's fully loaded?

[chris]

I posted something about this error about a week ago:

http://extjs.com/forum/showthread.php?t=4624

I'm using the Prototype adapter with Ext.Toolbar and I get the error in FF. Basically, I can trigger the error (with no other code besides the HTML and Ext/Prototype) by dragging the mouse over the Toolbar and then over a textarea input (see the original post for more details).

[tryanDLS]

While kicking the same type of problem around with someone else, we came up with a possible fix. Can you try and add autocomplete="off" to the text field and see what happens.

[amon]

It is an old Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=261423

With the autocomplete="off" hack it can be eliminated, but that is not valid.

[jack.slocum]

Thanks Amon, I have been looking for the source of it for a while. I have gotten it as well. It seems to be internal to FF and causes no problems, which is good.

The autocomplete="off" "hack" is of course to fix other FF errors.

[chris]

Originally Posted by jack.slocum

Thanks Amon, I have been looking for the source of it for a while. I have gotten it as well. It seems to be internal to FF and causes no problems, which is good.

In my example a Toolbar item stays highlighted though the mouse trails off into the textarea, leading me to think that whatever mouseover event that occurs to unhighlight the toolbar button is where the error might occur. Turning autocomplete off didn't seem to do anything either.

[amon]

You're welcome, Jack!
Anyway, the autocomplete='off' hack had fixed this error for me.