UIA Text pattern reports SupportedTextSelection_None on documents
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
If you query the UIA Text pattern's SupportedTextSelection property on a document, it returns SupportedTextSelection_None. This is because we don't expose the SELECTABLE_TEXT state on DocAccessibles in the core tree.
Assignee | ||
Comment 1•26 days ago
|
||
We already had code to expose SELECTABLE_TEXT in HyperTextAccessible, from which DocAccessible inherits.
However, DocAccessible overrides the method and doesn't call the HyperTextAccessible implementation.
We don't want to do that because it does work that isn't necessary for DocAccessible.
In addition, we need to use a different layout frame for the document.
See the code comments for details.
Specific code has been added to DocAccessible to expose this state.
This fixes the UIA Text pattern's SupportedTextSelection property on documents.
Assignee | ||
Comment 2•26 days ago
|
||
For now, the core SELECTABLE_TEXT state is only exposed on text containers, not on text leaves.
We may want to reconsider this at some point.
For now, just handle this case in the UIA code, since that's the only place it matters.
Comment 4•22 days ago
|
||
Backed out for causing failures at browser_accessibility_print_to_json.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/2993c64682bd621e8a0479c1176561bf3a1bd523
Failure log: https://treeherder.mozilla.org/logviewer?job_id=497386518&repo=autoland&lineNumber=2695
Assignee | ||
Updated•21 days ago
|
Comment 6•21 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e71f3c882012
https://hg.mozilla.org/mozilla-central/rev/9916a6e16cf0
Description
•