371705 - Blank page in Google Page Creator when trying to edit - NS_ERROR_DOM_WRONG_DOCUMENT_ERR

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[Martijn Wargers (dead)]

When trying to edit some page at pages.google.com, I get a blank page insted and this js erro:
Error: [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://pages.google.com/-/js/Vey9ixg4w__trog_edit_experimental.js Line: 248"]
Source File: http://pages.google.com/-/js/Vey9ixg4w__trog_edit_experimental.js
Line: 248
This is most likely a regression from fixing bug

Comment 1

[Ryan Jones-Ward [:sciguyryan]]

Actually could this be a regression from bug 366946 if it happened recently?

Comment 2

[Martijn Wargers (dead)]

No, I'm getting the same error with a 2007-02-02 trunk build, which is before your patch check-in from bug 366946.

Comment 3

[:Mook]

Attachment: Workaround greasemonkey script

Attaching a greasemonkey script I'm using to workaround this.  (I am still hoping Google will fix this on their side, of course, but wallpapering helps the pain.)

It should also work with sites with the same problem, as long as they are dealing with HTML elements...  It's a giant hack though.

Comment 4

[Pete Brunet]

The same error appears running
http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_InlineEditBox.html
I've noticed it in 5/6/7pre.  Runs OK in FF 2.0.0.4.

Comment 5

[Pete Brunet]

Regarding comment 4 the DOM look like:

    fieldset
      iframe
      . #document  <-- this has DesignMode on
      .   html
      .     head
      .     body
      .       div
      .         #text
      .         br
      textarea  <-- this is always hidden

Comment 6

[Martijn Wargers (dead)]

This is still a problem. :(
I really would like to see this kind of thing fixed before Firefox3 comes out, but there is no way to set a blocking flag for this.
Pete, probably the dojotoolkit issue should be filed as a separate bug, since this is supposed to be a problem with the website, not the browser.

Comment 8

[r.navalinskas]

It is still a problem in FF3 Beta3

Comment 9

[Biju]

(In reply to comment #8)
> It is still a problem in FF3 Beta3

I assume this is fixed by bug 418755. Please check.

Comment 10

[kripkenstein]

I am on FF3 Beta4 on Ubuntu Hardy and Google Pages appears to work fine now, I can edit pages, which before I could not.

Comment 11

[Biju]

fixed by bug 418755