Closed
Bug 1849776
Opened 1 years ago
Closed 1 years ago
Don't allocate DeferredContentEditableCountChangeEvent unnecessarily
Categories
(Core :: DOM: Core & HTML, task)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
118 Branch
| Tracking | Status | |
|---|---|---|
| firefox118 | --- | fixed |
People
(Reporter: mstange, Assigned: mstange)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sp3])
Attachments
(1 file)
In the profiles from bug 1844470 I saw allocations and frees of DeferredContentEditableCountChangeEvent but no time spent in DeferredContentEditableCountChangeEvent::Run. It turns out that Editor-TipTap has a lot of invocations to Document::ChangeContentEditableCount with aElement being nullptr.
|
Assignee | |
Comment 1•1 years ago
|
||
Pushed by mstange@themasta.com:
https://hg.mozilla.org/integration/autoland/rev/a1487474ef27
Don't enqueue DeferredContentEditableCountChangeEvent if aElement is nullptr. r=smaug
|
||
Comment 3•1 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 years ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
|
||
Updated•1 years ago
|
Whiteboard: [sp3]
|
||
Updated•1 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-530
You need to log in
before you can comment on or make changes to this bug.
Description
•