1327990 - Debugger doesn't work and devtools are completely broken by specific script (can't reopen toolbox)

Status: RESOLVED INVALID

(DevTools :: Debugger, defect)

Description

[arni2033]

>>>   My Info:   Win7_64, Nightly 48, 32bit, ID 20160416030220
STR_1:
1. Open url [1]
2. Open debugger (Ctrl+Shift+S)
3. Close devtools (F12). Open devtools (F12)

AR:  Step 3 - no visible action
ER:  Step 3 - devtools should open


STR_2:  (further experiments)
1. Open url [1]  (URL in the form above, which is the same)
2. Open debugger, open console in the same devtools tab (Escape key)
3. Open sidebar "Events"
4. Pause all scripts on page (F8). Then click on the page
5. Close devtools (F12). Open devtools (F12)

AR:  After Step 3 there're no events. After Step 4 there's console message "1". After Step 5 - nothing
ER:  Step 3 - "click" handler should be visible;  Step 4 - no messages;  Step 5 - devtools should open


STR_3:
1. Open http://imgur.com/0Cw7aKJ in a new tab [Tab1]
2. Disable internet connection
3. Open  debugger (Ctrl+Shift+S)
4. Close devtools (F12)
5. Open  devtools (F12)   [FAIL]

AR:  Step 5 - no visible action
ER:  Step 5 - devtools should open


Note:  This doesn't happen with pref "devtools.debugger.source-maps-enabled" set to false

> [1] data:text/html,<script src="data:text/javascript,onclick = function(){if(true)console.log(1)};//%2523 sourceMappingURL=/widget.js.map"></script>

Comment 1

[Justin [:JW_SoftvisionQA]]

I can not reproduce this issue on the current version of nightly. Can you please retest and post your findings?

Comment 2

[castiel743]

>>>   My Info:   Win7_64, Nightly 53, 32bit, ID 20170104030214 (2017-01-04)
Reproducible on the debugger shipped with release version.

To test the debugger shipped w/ release version, open about:config and set
"devtools.debugger.new-debugger-frontend" to "false". If Firefox developers will not fix such
usability bugs (I'm not aware of this) that prevent people from debugging and even using devtools,
then I think the right thing is to ignore this bug until events tab is implemented in the new debugger

Comment 3

[Justin [:JW_SoftvisionQA]]

WIth the information in Comment 2 I can reproduce this issue. Below is the results of MozRegression

 4:54.22 INFO: Last good revision: 482b9d04974a (2013-08-05)
 4:54.22 INFO: First bad revision: 1e381c91885d (2013-08-06)
 4:54.22 INFO: Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=482b9d04974a&tochan
ge=1e381c91885d

From the pushlog maybe it is 892168 ?

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

This report is related to the old Debugger UI, which is no longer available, closing.

Honza