Remove HyperTextAccessible::SelectionCount and SelectionBoundsAt
Categories
(Core :: Disability Access APIs, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
HyperTextAccessibleBase has unified implementations, so there shouldn't be a need to specialise for LocalAccessible. However, accessible/tests/mochitest/textselection/test_general.html fails, so there must be some differences between the implementations. We should either:
- Determine that this is a bug in the HyperTextAccessibleBase implementation and fix it; or
- Fix the test.
| Assignee | ||
Updated•4 months ago
|
| Assignee | ||
Comment 1•4 months ago
|
||
These are implemented in HyperTextAccessibleBase.
Having local and remote use the same implementation makes things simpler, more consistent, easier to test and easier to reason about.
This is also necessary in order to properly test the fix in the next patch.
This breaks the rare edge case of selecting only empty containers for LocalAccessible.
This never worked for RemoteAccessible anyway, which is the majority of content now.
Bug 1973154 has been filed for this.
Updated•4 months ago
|
Updated•4 months ago
|
| Assignee | ||
Comment 2•4 months ago
|
||
(In reply to James Teh [:Jamie] from comment #0)
- Determine that this is a bug in the HyperTextAccessibleBase implementation and fix it; or
See bug 1973154. Strictly speaking, it's a bug in the Base implementation, but it's rare and I don't think it should block this, especially given that we need it to test bug 1972539.
Comment 4•4 months ago
|
||
| bugherder | ||
Updated•3 months ago
|
Description
•