Closed
Bug 1625789
Opened 5 years ago
Closed 5 years ago
Optimize CustomElement constructors out from cycle collector graph when possible
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla77
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(1 file)
This shows up especially with browser windows which seem to use quite a few custom elements.
|
||
Updated•5 years ago
|
Priority: -- → P2
|
Assignee | |
Comment 1•5 years ago
|
||
Changing the summary a bit to match the change I'll do in this bug, and then followups will deal with smaller optimizations.
Summary: Optimize out CustomElementRegistry and the objects it keeps alive from cycle collector graph when possible → Optimize CustomElement constructors out from cycle collector graph when possible
|
|
Assignee | |
Comment 2•5 years ago
|
||
Using the method name GetExistingCustomElements() to match CustomElements(), even though
they both return CustomElementRegistry.
|
|
Assignee | |
Comment 3•5 years ago
|
||
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2018df8cdb6f
optimize CustomElement constructors out from cycle collection graph, r=mccr8
|
||
Comment 5•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in
before you can comment on or make changes to this bug.
Description
•