Closed
Bug 713211
Opened 13 years ago
Closed 5 years ago
Javascript error using Firebug
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: pauly, Unassigned)
Details
(Whiteboard: [10b1])
Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20100101 Firefox/10.0 Reproducible: always Steps to reproduce: 1. Launch Firefox 2. Install latest Firebug: http://getfirebug.com/releases/firebug/1.9/firebug-1.9.0b4.xpi 3. Open www.google.com 4. Press F12 to display the Firebug console 5. Go to Console and Script panels and enable them 6. Stay on the Script panel 7. Ctrl-R to reload 8. Click on lines 1 and 2 to set breakpoints. 9. Ctrl-R to reload 10. Click again on lines 1 and 2 to remove the breakpoints 11. Ctrl-R to reload Actual results: "No Javascript on this page" is displayed and the Console panel says: google is not defined [a,b];return false}};(function(){var a=google.j;window.onpopstate= Expected results: No errors should occur.
Comment 1•13 years ago
|
||
Could you get us a regression range for this?
Reporter | ||
Comment 2•13 years ago
|
||
The issue is reproducible on all Firefox versions (v4-v10). On Firefox 4 I used http://getfirebug.com/releases/firebug/1.7/firebug-1.7.0.xpi for testing since Firebug 1.9 is compatible only with Firefox 5 or higher.
Comment 3•12 years ago
|
||
OK, I see the problem too. It looks like users can work around by pressing Ctrl+R again. I notice that on step 9, the code is actually paused at one of the breakpoints, and if I continue and make sure the code isn't paused, then it works correctly. So it looks like there is some glitch, possibly a race, where the code isn't seen if paused at a breakpoint. I think it may be a Firebug bug rather than a JS engine bug, although I'm not sure.
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Comment 4•5 years ago
|
||
Firebug is EOL, therefore resolving as Invalid.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•