Closed
Bug 1227305
Opened 10 years ago
Closed 9 years ago
ReferenceError: can't access lexical declaration `max' before initialization causes "DOM Inspector" to stop working
Categories
(Other Applications :: DOM Inspector, defect)
Tracking
(firefox44 unaffected, firefox45 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox44 | --- | unaffected |
| firefox45 | --- | affected |
People
(Reporter: alice0775, Assigned: philip.chee)
References
Details
(Keywords: regression)
Attachments
(2 files)
Steps To Reproduce:
1. Disabled e10s
2. Install "Dom Inspector" and restart
3. Open with "Dom Inspector"
--- observe Browser Console
4. Optionally, Right click on a element in Dom Tree
"Delete" context menu is not enabled.
Actual Results:
ReferenceError: can't access lexical declaration `max' before initialization
DVr_GetSelectedIndexes() dom.js:1589
DVr_GetSelectedNodes() dom.js:1570
DVr_IsCommandEnabled() dom.js:236
updateCommand() inspector.xml:159
updateAllCommands() inspector.xml:140
onxblfocus() inspector.xml:386
notifyViewerReady() inspector.xml:577
DVr_initialize() dom.js:177
DOMViewer_initialize() dom.js:45
1 dom.js:1589:31
Expected Results:
No error,
"Delete" context menu should be enabled at step4.
Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=ea3f6bb82e6c69f514fab728ed2be8e38ccfd256&tochange=ce0741b494a7
Regressed by: Bug 1216623
| Assignee | ||
Updated•9 years ago
|
Summary: "DOM Inspector" stops working → ReferenceError: can't access lexical declaration `max' before initialization causes "DOM Inspector" to stop working
| Assignee | ||
Comment 1•9 years ago
|
||
| Assignee | ||
Updated•9 years ago
|
Attachment #8691416 -
Flags: review?(neil)
Updated•9 years ago
|
Attachment #8691416 -
Flags: review?(neil) → review+
| Assignee | ||
Comment 2•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Hi, how does this landing align with the Inspector releases? Where can we expect this to be shipped in a relase?
Assignee: nobody → philip.chee
| Assignee | ||
Comment 4•9 years ago
|
||
(In reply to :aceman from comment #3)
> Hi, how does this landing align with the Inspector releases? Where can we
> expect this to be shipped in a release?
Usually we release a new version when:
1. We have enough changes to justify a new release, or
2. We have one or more compatibility fixes due to Gecko changes in newer Firefoxes.
I guess this bug would qualify as #2.
Comment 6•9 years ago
|
||
Can somebody attach a working build of the xpi please? I wasn't able to build one (stripping META-inf and zipping as usual did not do the job and caused the tool menu to vanish)
Comment 7•9 years ago
|
||
(In reply to Axel Grude [:realRaven] from comment #6)
> Can somebody attach a working build of the xpi please? I wasn't able to
> build one (stripping META-inf and zipping as usual did not do the job and
> caused the tool menu to vanish)
Sorry I meant tool menu entry for the DOM inspector.
| Assignee | ||
Comment 8•9 years ago
|
||
(In reply to Axel Grude [:realRaven] from comment #6)
> Can somebody attach a working build of the xpi please? I wasn't able to
> build one (stripping META-inf and zipping as usual did not do the job and
> caused the tool menu to vanish)
Flags: needinfo?(axelg)
Attachment #8750733 -
Flags: feedback?(axelg)
Comment 9•9 years ago
|
||
1) Works in Release Version of Firefox
result: success
2a) I cannot test in Fx beta 47.0b3 because we cannot bypass Addons with missing signatures anymore so it refused to install :( - unfortunately the promised unbranded versions are no available online
result: N/A no test result available.
2b) Tested in Thunderbird 45.1 beta - it fixes the "max" problem and I am able to cut/paste DOM nodes.
result: SUCCESS
3) Trying to test in developer edition v 48.0a2
there seems to be a fresh bug there which leads to the DOM inspector not being shown. I will raise that one separately when I get time.
result: N/A - no test result available.
TypeError: content is null
oncommand()browser.xul:1
1browser.xul:1:1
Flags: needinfo?(axelg)
Comment 10•9 years ago
|
||
I keep getting needinfo feedback request mails although I cleared the dlag. can somebody advise what to do about this?
Comment 11•9 years ago
|
||
You still have feedback request on attachment https://bugzilla.mozilla.org/attachment.cgi?id=8750733 . Set in comment 8. You only cleared the needinfo flag.
Comment 12•9 years ago
|
||
Comment on attachment 8750733 [details]
inspector@mozilla.org-2.0.17pre.xpi
Looks good to me. When are you releasing?
Attachment #8750733 -
Flags: feedback?(axelg) → feedback+
You need to log in
before you can comment on or make changes to this bug.
Description
•