370508 - NS_ERROR_DOM_WRONG_DOCUMENT_ERR when I double click to edit a note in google notebook on linux

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Michael]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2) Gecko/20070206 GranParadiso/3.0a2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a2) Gecko/20070206 GranParadiso/3.0a2

On Linux, when I double click to edit a note it crashes.
On windows, when I double click to edit the note goes into edit mode but the note is blank.

Even if a node is not imported, it should not crash the browser like it does on linux.

I am referring to the 3.0a2 build on both platforms.

This is related to :
"Moving DOM nodes between documents now requires a call to importNode or adoptNode as per the DOM specification."

In the error console I get :
"Error: uncaught exception: [Exception... "Node cannot be used in a document other than the one in which it was created"  code: "4" nsresult: "0x80530004 (NS_ERROR_DOM_WRONG_DOCUMENT_ERR)"  location: "http://www.google.com/notebook/js/4253011231-notebook_en_binary.js Line: 328"]"

Reproducible: Always

Steps to Reproduce:
1. login into http://www.google.com/notebook
2. double click on an existing note ( or try to create a new one )
3.
Actual Results:  
browser crashes

Expected Results:  
thrown an error that the node was not imported

Comment 1

[timeless]

complain to google.

Comment 2

[Michael]

What ever google is doing, they should not be able to crash the browser using javascript. 

It should throw an exception, not crash the browser.

Comment 3

[timeless]

i don't see any indication that it crashed. all you said was NS_ERROR_DOM_WRONG_DOCUMENT_ERR which isn't a crash.

where's your talkback incident id?

Comment 4

[Michael]

the NS_ERROR_DOM_WRONG_DOCUMENT_ERR is from windows, on Linux it crashes.

I don't know the talkback incident id, but I did submit one. How can I search the Talkback database?

Comment 5

[Martijn Wargers (dead)]

Michael, does it still crash for you in current trunk builds?

Comment 6

[Biju]

Related Tech Evangelism Bug 366336 

Comment 7

[Michael]

Google has since put out a new version of Google notebook which does not cause the browser to crash, so this bug is no longer reproducible.

Comment 8

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.10 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 9

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.