Closed
Bug 765110
Opened 13 years ago
Closed 13 years ago
TextLeafAccessibleWrap is never instanciated
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
mozilla16
Tracking | Status | |
---|---|---|
firefox15 | --- | fixed |
People
(Reporter: hub, Assigned: capella)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
1.47 KB,
patch
|
tbsaunde
:
review+
akeybl
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
TextLeafAccessibleWrap is never instanciated. Only the MSAA backend define the class, but the nsAccessibilityService implementation will not instanciate it, sticking to TextLeafAccessible.
Assignee | ||
Comment 1•13 years ago
|
||
I imagine this is just this small change ... coidng is simple, but how do I test it / see the before and after effects for myself? I'm tinkering around with DOMInspector and ACCProbe ... but they're relatively new tools to me, and maybe I just don't know where to look ....
Updated•13 years ago
|
Attachment #637091 -
Flags: review?(hub) → review+
Assignee | ||
Comment 2•13 years ago
|
||
(regression from bug 745428 - my bad!)
Push to TRY:
https://tbpl.mozilla.org/?tree=Try&rev=161957dc4af5
Reporter | ||
Comment 3•13 years ago
|
||
Now I filed the bug but never tested anything. I just found it out trying to do stuff on Mac.
Does it really have an impact on Windows?
Assignee | ||
Comment 4•13 years ago
|
||
Dang ... other people
https://tbpl.mozilla.org/?tree=Try&rev=da6c03ac176f
Comment 5•13 years ago
|
||
(In reply to Mark Capella [:capella] from comment #1)
> Created attachment 637091 [details] [diff] [review]
> Patch (v1)
>
> I imagine this is just this small change ... coidng is simple, but how do I
> test it / see the before and after effects for myself? I'm tinkering around
> with DOMInspector and ACCProbe ... but they're relatively new tools to me,
> and maybe I just don't know where to look ....
This class implements ISimpleDOMText interface, I don't think we have tools to test it.
Please make sure to get an approval for aurora where we regressed since this interface is used by AT.
Hub, thanks for the catch.
Assignee | ||
Comment 6•13 years ago
|
||
Target Milestone: --- → mozilla16
Comment 7•13 years ago
|
||
Sorry, this merged yesterday, but I completely forgot to do the bug marking:
https://hg.mozilla.org/mozilla-central/rev/dcf8693ba5e1
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
Comment on attachment 637091 [details] [diff] [review]
Patch (v1)
[Approval Request Comment]
Bug caused by (feature/regressing bug #): 745428
User impact if declined: certain assistive technology on windows may have trouble accessing text of web page elements.
Testing completed (on m-c, etc.): yes
Risk to taking this patch (and alternatives if risky): extremely low. it changes nothing on platforms other than windows. On windows there nothing is removed, but an interface that we stopped exposing to screen readers will be exposed again. nothing has changed in the implementation, so it should be very safe.
String or UUID changes made by this patch: none
Attachment #637091 -
Flags: approval-mozilla-aurora?
Comment 9•13 years ago
|
||
Comment on attachment 637091 [details] [diff] [review]
Patch (v1)
[Triage Comment]
Low risk a11y fix for a FF15 regression. Approved for Aurora 15.
Attachment #637091 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 10•13 years ago
|
||
status-firefox15:
--- → fixed
Updated•12 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•