Closed
Bug 761574
Opened 14 years ago
Closed 13 years ago
Debugger Closing after Opening it immediately on Mac (a11y)
Categories
(DevTools :: Debugger, defect, P1)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 668469
People
(Reporter: rcampbell, Assigned: hub)
References
Details
In current nightly, FF16.0a, opening the debugger causes an assertion in mozAccessible.mm which causes the debugger to close immediately.
| Reporter | ||
Updated•14 years ago
|
Severity: normal → critical
OS: All → Mac OS X
Priority: -- → P1
Hardware: All → x86
Comment 1•14 years ago
|
||
Rob was this some kind of assertion related to a11y being instantiated?
| Reporter | ||
Comment 2•14 years ago
|
||
it's easy to test! With the Big Global Accessibility option enabled, try opening the Debugger in Firefox and check the Error Console.
Comment 3•14 years ago
|
||
(In reply to David Bolter [:davidb] from comment #1)
Assertion failure in -[mozRootAccessible didReceiveFocus], /fx-team/accessible/src/mac/mozAccessible.mm:587
Comment 4•14 years ago
|
||
OK thanks. Hub, can you take this one?
| Assignee | ||
Comment 5•14 years ago
|
||
I get that assert often (it is non fatal). I have no idea why it is in there. DOM Inspector and mochitest triggers it too.
Comment 6•14 years ago
|
||
The assertion is:
NSAssert1(![self accessibilityIsIgnored], @"trying to set focus to ignored element! (%@)", self);
accessibilityIsIgnored method returns true for any accessible object having a role that isn't mapped to mac a11y.
The fix is to make accessibilityIsIgnored method to check the presence of focusable state.
Hub, wanna take the bug?
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → hub
| Assignee | ||
Comment 7•14 years ago
|
||
mozRootAccessible is the accessible created for the CHROME_WINDOW role, that is ignored.
I believe this is wrong as it should be the NSWindow (ie the window in MacOS).
| Assignee | ||
Comment 8•14 years ago
|
||
I can reproduce after fixing the error leading to the assert. I don't know what is happening, nor have any idea if the debug messages are relevant or not.
I use mozilla-inbound.
| Assignee | ||
Comment 9•14 years ago
|
||
(I also have a patch to disable the VO whitelisting that have been introduced between the moment the bug was reported and now... as well as have a11y enabled explicitely as it no longer is)
| Assignee | ||
Comment 10•14 years ago
|
||
actually I realize, I didn't have the patch fixing the assert unlike I said in comment 8. With or without I don't get the assert but I do get the bug.
| Assignee | ||
Comment 11•13 years ago
|
||
The assert mentionned in comment 6 is bug 668469
Depends on: 668469
| Reporter | ||
Comment 12•13 years ago
|
||
Hub, is this still a problem for us? If mac a11y has been disabled, the assertion should go away and things should behave as they should, right?
| Reporter | ||
Comment 13•13 years ago
|
||
followup question: Should this be an a11y bug and not specifically the Debugger?
Comment 14•13 years ago
|
||
(In reply to Rob Campbell [:rc] (:robcee) from comment #13)
> followup question: Should this be an a11y bug and not specifically the
> Debugger?
yes, I think focusable stuffs should be never ignored.
Hub, are you ok with approach from comment #6?
| Assignee | ||
Comment 15•13 years ago
|
||
Alex, seems to be reasonable.
| Assignee | ||
Comment 16•13 years ago
|
||
I believe this is an actual dupe of bug 668469 that has just been fixed in central.
Let me know if you still encounter problems. If not, I'll mark this one as dupe.
Thanks.
Comment 17•13 years ago
|
||
dupe per comment #16
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•