Clean up HyperTextAccessible methods now that all boundaries are supported by TextLeafPoint
Categories
(Core :: Disability Access APIs, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ctw-m1])
Attachments
(2 files)
With the exception of BOUNDARY_CHAR which must be handled specially due to embedded objects being characters, HyperTextAccessibleBase now uses TextLeafPoint for all other boundaries. This means we can remove a bunch of case statements and if checks.
Also, HyperTextAccessible isn't currently using HyperTextAccessibleBase for BOUNDARY_CHAR when the cache is enabled. This was an oversight. However, fixing that surfaced a bug which I hadn't previously noticed.
Assignee | ||
Comment 1•3 years ago
|
||
We need to adjust the offset if the caret is at the end of the line in this case.
Assignee | ||
Comment 2•3 years ago
|
||
This also causes HyperTextAccessible to use HyperTextAccessibleBase for BOUNDARY_CHAR when the cache is enabled.
The fact that we weren't doing this already was an oversight.
Comment 4•3 years ago
|
||
Backed out 4 changesets (bug 1730090, bug 1755604, bug 1755420) for causing build bustages in accessible/base/TextLeafRange.cpp
Backout link: https://hg.mozilla.org/integration/autoland/rev/6938c3b26d145c7e2c77f078566463df66d45359
NFO - In file included from Unified_cpp_accessible_base1.cpp:29:
[task 2022-02-18T06:06:16.637Z] 06:06:16 ERROR - /builds/worker/checkouts/gecko/accessible/base/TextLeafRange.cpp:361:15: error: expected unqualified-id
[task 2022-02-18T06:06:16.637Z] 06:06:16 INFO - if (RefPtr{aAcc->DisplayStyle()} == nsGkAtoms::block ||
Assignee | ||
Updated•3 years ago
|
Comment 6•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/86335bec494a
https://hg.mozilla.org/mozilla-central/rev/fac8cd3d8e8d
Description
•