This is with build Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7+) Gecko/20020108. If you right-click in a normal Mozilla browser window, you get as a message the following: Deprecated method document.getSelection() called. Please use window.getSelection() instead. If you right-click in a DOM Inspector browser panel of the same document, you get a whole bunch of this warning: Warning: reference to undefined property this.target.ownerDocument.getSelection Source File: chrome://communicator/content/nsContextMenu.js Line: 636 and these two errors: Error: this.target.ownerDocument.getSelection is not a function Source File: chrome://communicator/content/nsContextMenu.js Line: 636 Error: gContextMenu has no properties Source File: chrome://editor/content/editorApplicationOverlay.js Line: 64 I think what is happening here is the wrong window object, or the wrong document object, are what the objects are referring to. Bug 119023 describes the same problem with different symptoms, if I'm right in this bug. If the event handling was running from the browser portion of DOM-Inspector, probably we wouldn't be seeing this or bug 119023. Opinions? Does anyone understand what I'm saying, or can say it more clearly?
Original symptoms of this bug are no longer present in recent Mozilla nightly. Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030207 However, now the context menu won't work in the browser pane. Is that intentional?
*** Bug 132048 has been marked as a duplicate of this bug. ***
Well, this bug is still valid; bug 132048 is another symptom of the same problem. Moving URI and testcase notes to this bug. (from neil) Steps to reproduce problem: 1. Open DOM Inspector 2. Inspect the above URL Expected results: document loads in DOM Inspector's Browser Actual results: DOM Inspector resizes while loading document
Mass re-assigning bugs to firstname.lastname@example.org
Assignee: hewitt → dom.inspector
Status: ASSIGNED → NEW
Assignee: dom-inspector → nobody
QA Contact: timeless → dom-inspector
You need to log in before you can comment on or make changes to this bug.