Closed
Bug 1811963
Opened 1 year ago
Closed 1 year ago
CustomElementData::Traverse should use NoteXPCOMChild for mElementInternals
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
Details
Attachments
(1 file)
CustomElementData::Traverse uses NoteNativeChild for mElementInternals, which has type ElementInternals. However, ElementInternals is an nsISupports class, so this should use NoteXPCOMChild instead. I don't think this is an issue now, but it could cause problems if ElementInternals had any subclasses with their own CC participant. I audited all of the other direct calls to NoteNativeChild (there aren't a lot because most things go through the template magic that picks the right one) and the rest were all for non-nsISupports classes, as is appropriate.
Assignee | ||
Comment 1•1 year ago
|
||
ElementInternals is an nsISupports class, so this should use NoteXPCOMChild.
Pushed by amccreight@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a48f2317a143 CustomElementData::Traverse should use NoteXPCOMChild for mElementInternals. r=smaug
Comment 3•1 year ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•