The default bug view has changed. See this FAQ.

TextLeafAccessibleWrap is never instanciated

RESOLVED FIXED in Firefox 15

Status

()

Core
Disability Access APIs
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: hub, Assigned: capella)

Tracking

Trunk
mozilla16
x86
All
Points:
---

Firefox Tracking Flags

(firefox15 fixed)

Details

(Whiteboard: [qa-])

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
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

5 years ago
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 ....
Assignee: nobody → markcapella
Status: NEW → ASSIGNED
Attachment #637091 - Flags: review?(hub)
Attachment #637091 - Flags: review?(hub) → review+
Blocks: 745428
(Assignee)

Comment 2

5 years ago
(regression from bug 745428 - my bad!)

Push to TRY:
https://tbpl.mozilla.org/?tree=Try&rev=161957dc4af5
(Reporter)

Comment 3

5 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

5 years ago
Dang ... other people 
https://tbpl.mozilla.org/?tree=Try&rev=da6c03ac176f

Comment 5

5 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

5 years ago
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=dcf8693ba5e1
Target Milestone: --- → mozilla16
Sorry, this merged yesterday, but I completely forgot to do the bug marking:
https://hg.mozilla.org/mozilla-central/rev/dcf8693ba5e1
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
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

5 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+
http://hg.mozilla.org/releases/mozilla-aurora/rev/a45c99cca5e5
status-firefox15: --- → fixed

Updated

5 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.