My favorites | Sign in
Project Home Wiki Issues
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 5184: Accessibility Enhancements (firebug.a11y.enable) cause loss of script break indication in some cases (Script tab stays black)
1 person starred this issue and may be notified of changes. Back to list
Status:  Triaged
Owner:  ----

Sign in to add a comment
Reported by, Jan 26, 2012
When a script breaks, Firebug is supposed to catch the user's attention by making the Script tab yellow (rather than black) and by switching to the Script tab if another tab is active. This does not happen in certain situations.

For example, this can happen when a breakpoint is set and the user is in the HTML tab. There are 2 conditions for this to happen:
1. Option "Enable Accessibility Enhancements" (firebug.a11y.enable) is enabled
2. The user did not go to the Script tab since the page was loaded.

2. implies that a break condition must have been set in advance.

This happens under Iceweasel 10.0b5 with either version 1.9.0 or 1.10a1. I also reproduced with Firefox 9.

The attached page can be used to verify by setting a breakpoint on line 7 "console.log("Hi");" and clicking "Test breakpoint".

This can also be observed on by setting a breakpoint on line 15 ("B3();") and clicking "Deep error". Load the page, set the breakpoint, go to the HTML tab, reload and click. Notice that there is absolutely no indication that script broke.


307 bytes   View   Download
Jan 26, 2012
I can confirm that. Thanks for the test case. I split this issue into two, because their symptoms are different.
So this issue will just cover the part, in which the accessibility enhancements are enabled, while issue 5186 covers the other part.

Steps to reproduce:
1. Open Firebug on the test page
2. Check Firebug Menu > Options > Enable Accessibility Enhancements
3. Enable and switch to the Script panel
4. Reload the page
5. Set a breakpoint at line 7 ("console.log("Hi");")
6. Switch to the HTML panel
7. Reload the page
8. Click on "Test breakpoint"
   => The script execution is stopped (OK)
   => Firebug doesn't switch to the Script panel (BUG)
   => The Script tab is not marked in orange as sign, that the script execution stopped (BUG)
9. Switch to the Script panel
   => The Script tab is marked in orange (OK)
   => Line 7 is not marked, even when the execution is stopped there (BUG)

=> Script execution break is not displayed correctly, if accessibility enhancements are enabled

Status: Triaged
Labels: Type-Defect script Test-case-available
Jan 26, 2012
Thanks. I agree, there are more issues that can be seen here than the lack of notification. Indeed, even once one switches to the Script tab, the debugger is not showing OK (empty panels, no indication of current line).

For what it's worth, I did not experience, at least knowingly, issue 5186. What prompted me to report this is really what I originally reported.
The additional problems of debugger display you mention here would be good to fix too, but they're not specific to this case.
Mar 23, 2013
Project Member #3
(No comment was entered for this change.)
Apr 4, 2013
Project Member #4
(No comment was entered for this change.)
Labels: 1.9.0 1.10-a1
Sign in to add a comment

Powered by Google Project Hosting