The accessible hyperlink implementation seems to have vanished in Linux
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox116 | --- | unaffected |
firefox117 | + | fixed |
firefox118 | + | fixed |
firefox119 | --- | fixed |
People
(Reporter: jdiggs, Assigned: Jamie)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details |
Steps to reproduce:
- Load some content
- Use Accerciser to examine the implemented interfaces for elements on the page
Expected results: The hyperlink interface would be implemented.
Actual results: The hyperlink interface is not implemented.
Impact: Orca uses the hyperlink interface in its logic to piece together lines, specifically to connect a given child with its offset in the parent. In at least one case (so far), Orca is now failing to present content it used to present prior to the regression.
Regression range:
117.01a 07-30: good
117.01a 07-31: bad
Assignee | ||
Comment 1•1 year ago
|
||
I... have no idea what could have happened here.
Assignee | ||
Comment 2•1 year ago
|
||
[Tracking Requested - why for this release]: Some content is not accessible to Orca screen reader users.
Assignee | ||
Comment 3•1 year ago
|
||
After some digging, I'm fairly certain (but haven't verified) that this is a regression introduced by bug 1779578.
I think the problem is that we now call ProxyCreated before we attach to the parent, but IsLink (used to determine whether something should expose the HyperLink interface and called when the ATK object is created) depends on the presence of the parent!
Given the proximity to rc here, the simplest solution might be to back out bug 1779578 from 117.
Comment 4•1 year ago
|
||
Set release status flags based on info from the regressing bug 1779578
Assignee | ||
Comment 5•1 year ago
|
||
Sorry Joanie. I know there's been a bit of churn lately. On the flip side, I fixed most of the text bugs. :)
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 6•1 year ago
|
||
Urgh, sorry. Bugzilla submission screw-up on my part.
Assignee | ||
Comment 7•1 year ago
|
||
This is what we did before the fix for bug 1779578.
Failure to do this meant that RemoteAccessible::IsLink() returned false even for a child of a HyperText Accessible, which meant the ATK object was created without the HyperLink interface.
Assignee | ||
Comment 8•1 year ago
|
||
For some reason, I couldn't get Accerciser to show me the Firefox tree. There's probably some pebcak here, but I couldn't figure out what. :( Joanie, would you mind taking this try build for a spin and telling me whether it fixes the problem?
Reporter | ||
Comment 9•1 year ago
|
||
The try build does fix the problem. Thanks!
As for the text bugs: I had noticed that my debug output had a lot fewer (maybe zero?) instances of "FAIL: Bad results for text at offset" in it. Those lines come from Orca's sanity checking all Gecko text results and finding failures. Thus their absence suggests I might be able to remove (or at least turn off by default) those checks. Super cool and thanks!!
Updated•1 year ago
|
Comment 10•1 year ago
|
||
(In reply to James Teh [:Jamie] from comment #3)
Given the proximity to rc here, the simplest solution might be to back out bug 1779578 from 117.
Given where we are in the cycle and the note about risk mentioned in bug 1779578 comment 15, I'm inclined to agree about letting this bake for another cycle. I'll revert bug 1779578 from Beta for 117.0b9.
Comment 11•1 year ago
|
||
Fixed for Fx117 by backout.
https://hg.mozilla.org/releases/mozilla-beta/rev/4a0c1a095483
Comment 12•1 year ago
|
||
:jamie Fx118 is now the Beta, any timing concerns wtih landing this patch and requesting beta uplift?
Assignee | ||
Comment 13•1 year ago
|
||
I'm just waiting on review, which is a bit slow due to All Hands and the like, but I don't anticipate any problems.
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
bugherder |
Comment 16•1 year ago
|
||
The patch landed in nightly and beta is affected.
:Jamie, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox118
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 17•1 year ago
|
||
Comment on attachment 9349344 [details]
Bug 1848991: Attach a RemoteAccessible to its parent before calling ProxyCreated.
Beta/Release Uplift Approval Request
- User impact if declined: Certain content isn't presented at all with the Orca screen reader on Linux.
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Restores some previous behaviour before the regressing bug.
- String changes made/needed:
- Is Android affected?: No
Comment 18•1 year ago
|
||
Comment on attachment 9349344 [details]
Bug 1848991: Attach a RemoteAccessible to its parent before calling ProxyCreated.
Approved for 118.0b5, thanks.
Comment 19•1 year ago
|
||
uplift |
Comment 20•1 year ago
|
||
bugherder uplift |
Description
•