Closed
Bug 1816242
Opened 1 year ago
Closed 1 year ago
Optimize nsRange::ContentRemoved in some common cases
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
112 Branch
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(1 file)
IsInclusiveDescendantOf calls can be rather slow, and it seems some js/html based code editors remove often nodes which are something like
<div>text</div>.
And mRoot shouldn't be updated to the same value it already has.
Assignee | ||
Comment 1•1 year ago
|
||
Depends on D169548
Updated•1 year ago
|
Attachment #9317186 -
Attachment description: WIP: Bug 1816242 - Optimize nsRange::ContentRemoved in some common cases, r=emilio → Bug 1816242 - Optimize nsRange::ContentRemoved in some common cases, r=emilio
Pushed by opettay@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dee626e06939 Optimize nsRange::ContentRemoved in some common cases, r=emilio
Comment 3•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•