Closed
Bug 604722
Opened 14 years ago
Closed 14 years ago
Web Console won't open on chrome content
Categories
(DevTools :: General, defect)
DevTools
General
Tracking
(blocking2.0 -)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: rcampbell, Assigned: rcampbell)
Details
(Whiteboard: [Web-Console-Testday])
Attachments
(1 file, 3 obsolete files)
5.21 KB,
patch
|
rcampbell
:
review+
|
Details | Diff | Splinter Review |
Opening the Web Console on about: or chrome:// URIs gave us a chrome-enabled console. This stopped working as of October 14th. Opening the Console on about:config now produces: Error: (void 0) is undefined Source File: chrome://browser/content/tabbrowser.xml Line: 257 in Error Console.
Assignee | ||
Comment 1•14 years ago
|
||
nominating for blocking final. This unintended feature turned out to be a real help for chrome development. Also, the regression should probably be found as it may cause other undesirable side-effects.
blocking2.0: --- → ?
Assignee | ||
Comment 2•14 years ago
|
||
the error message is from this bug: [Bug 604210] Referencing property of undefined produces cryptic "(void 0) is undefined" message Accessing a property of an undefined object. Looks like we're passing wrappedJSObject to the contentWindow.document in HUDService.jsm, line 2967. http://hg.mozilla.org/mozilla-central/annotate/00e90d9720c8/toolkit/components/console/hudservice/HUDService.jsm#l2967 trying unwrap() as I have a feeling this is no longer being wrapped in chrome documents.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → rcampbell
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•14 years ago
|
||
still need a unittest for this
Attachment #483565 -
Flags: review?(gavin.sharp)
Assignee | ||
Comment 4•14 years ago
|
||
missed the Patch flag
Attachment #483565 -
Attachment is obsolete: true
Attachment #483566 -
Flags: review?(gavin.sharp)
Attachment #483565 -
Flags: review?(gavin.sharp)
Comment 5•14 years ago
|
||
This wouldn't happen to be covered by the tests at http://hg.mozilla.org/mozilla-central/rev/29c228a4d7eb#l1.28 would it?
Assignee | ||
Comment 6•14 years ago
|
||
no, although we filed bug 604431 and bug 604536 to fix code completion and turn those tests back on again. We didn't have a test to verify the console worked on chrome content pages because it was an unintended feature.
Assignee | ||
Comment 7•14 years ago
|
||
removed the unwrap function. Wasn't necessary after all.
Attachment #483566 -
Attachment is obsolete: true
Attachment #483582 -
Flags: review?(gavin.sharp)
Attachment #483566 -
Flags: review?(gavin.sharp)
Updated•14 years ago
|
Attachment #483582 -
Flags: review?(gavin.sharp) → review+
Updated•14 years ago
|
Attachment #483582 -
Flags: approval2.0+
Comment 8•14 years ago
|
||
This should land with a test.
Comment 9•14 years ago
|
||
Will certainly add a test in the spreadsheet
Assignee | ||
Updated•14 years ago
|
Whiteboard: [needs test]
Assignee | ||
Comment 10•14 years ago
|
||
carrying review forward. Now with unittest. Going to do a couple more tests on the test code and then can land.
Attachment #483582 -
Attachment is obsolete: true
Attachment #484702 -
Flags: review+
Assignee | ||
Updated•14 years ago
|
Keywords: checkin-needed
Whiteboard: [needs test]
Assignee | ||
Comment 11•14 years ago
|
||
Comment on attachment 484702 [details] [diff] [review] [checked-in] Chrome Console + Test http://hg.mozilla.org/mozilla-central/rev/7a48f839ccf1
Attachment #484702 -
Attachment description: Chrome Console + Test → [checked-in] Chrome Console + Test
Assignee | ||
Updated•14 years ago
|
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
Whiteboard: [Web-Console-Testday]
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•