View Full Version : Errormessage in Firebug: NS_ERROR_XPC_JS_THREW_STRING
Wolfgang
04-18-2007, 04:29 AM
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.
[Exception... "'Die Erlaubnis für das Lesen der Eigenschaft HTMLDivElement.nodeType wurde verweigert' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]
it translates into soemthing like this:
"Exception: The request to read the property HTMLDivElement.nodeType was denied, when calling method:[nsIDOMEventListener::handleEvent]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "<unknown>" data: no]"
thejoker101
04-18-2007, 09:13 AM
I've had that message too, from time to time. Not sure what it means though or what causes it.
mystix
04-18-2007, 11:32 AM
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
04-18-2007, 01:39 PM
Is it possible you're trying to access the document before it's fully loaded?
chris
04-18-2007, 04:41 PM
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
04-18-2007, 05:02 PM
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.
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
04-18-2007, 07:12 PM
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
04-18-2007, 07:34 PM
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.
You're welcome, Jack! :)
Anyway, the autocomplete='off' hack had fixed this error for me.
franzisk
05-26-2007, 06:31 AM
outocomplete='off' did not fix the error for me, it's becoming boring to clear this all the time.
I have lots of components (mainly ComboBoxes) and tried that solution with no success.
I am kinda hating this error already :(
I found that taking 'trackMouseOver: true,' out of the EditorGrid component fixes this.
Regards,
Ben
der Hase
10-23-2007, 08:16 AM
'trackMouseOver:false' helped me too.
Foggy
11-08-2007, 09:06 AM
Exactly, if you want you can reproduce this error on every editable grid if you set up trackMouseOver: true
and try to edit any cell...
Maybe this is not only a FF bug? :">
linizou
01-29-2008, 04:02 AM
It work , thanks
vBulletin® v3.6.7, Copyright ©2000-2009, Jelsoft Enterprises Ltd.