Display StaticRanges in custom highlights
Categories
(Core :: DOM: Selection, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: jjaschke, Assigned: jjaschke)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Currently StaticRange
s of custom highlights are not painted. This is due to nsINode::IsSelected()
not taking them into account and returning false. This should be solvable by moving some logic from nsRange
to AbstractRange
.
Assignee | ||
Comment 1•2 years ago
|
||
With this change, Selections are also registered into StaticRanges,
ultimately making them visible to nsINode::IsSelected()
,
which is necessary to paint them.
Assignee | ||
Comment 2•2 years ago
|
||
In order to support StaticRange
s, which are not MutationObserver
s, RangeBoundaries need to have an alternative way of ensuring that mRef
points to the correct node.
This is now done by validating mRef
every time Ref()
is called using the parent and offset.
For performance reasons, this is disabled by default and should only be used for StaticRange
s.
Updated•2 years ago
|
Comment 4•2 years ago
•
|
||
Backed out 3 changesets (Bug 1828469) for causing assertion in RangeBoundary.h
Log: https://treeherder.mozilla.org/logviewer?job_id=416686748&repo=autoland&lineNumber=13518
Crashtests: https://treeherder.mozilla.org/logviewer?job_id=416687272&repo=autoland&lineNumber=6648
Backout: https://hg.mozilla.org/integration/autoland/rev/70a155709dde9d2f0a44362e8841757244b86928
Comment 6•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b1014972dcb6
https://hg.mozilla.org/mozilla-central/rev/d1863c09bc4e
Assignee | ||
Updated•2 years ago
|
Description
•