Closed
Bug 1325279
Opened 7 years ago
Closed 7 years ago
Put the reaction queue in CustomElementData structure instead of using a map
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: jdai, Assigned: edgar)
References
Details
(Whiteboard: dom-ce-m2 )
Attachments
(1 file, 1 obsolete file)
6.65 KB,
patch
|
wchen
:
review+
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a follow-up of Bug #1309184 comment #22 +++ > + typedef nsTArray<nsAutoPtr<CustomElementReaction>> ReactionQueue; > + typedef nsClassHashtable<nsISupportsHashKey, ReactionQueue> > + ElementReactionQueueMap; > + > + ElementReactionQueueMap mElementReactionQueueMap; Elements have a structured called CustomElementData in the slots, you may be able put the reaction queue in that structure instead of using a map, but it will require a bit of refactoring to create the CustomElementData a bit earlier when we add elements to the reactions stack.
Updated•7 years ago
|
Whiteboard: dom-ce-m2
Comment 1•7 years ago
|
||
Per project discussion, this is a nice-to-have refactoring, not necessarily being in the project MVT, so removing dom-ce-m2 whiteboard.
Whiteboard: dom-ce-m2
Assignee | ||
Comment 2•7 years ago
|
||
Bug 1347446 makes accessing ElementReactionQueue in CustomElementRegistry becomes a bit non-trival (have to get it via DocGroup) and bug 1299363 part 2 patch has already refactored the creation time of CustomElementData, so I am going to handle this change in bug 1299363 (part 6 patch). Then we can just get reaction queue from Element.
Assignee | ||
Updated•7 years ago
|
Assignee: jdai → echen
Assignee | ||
Comment 3•7 years ago
|
||
I planed to handle this bug in bug 1299363. But other bugs are blocked by this change, so I move the patch back to this bug in order to let other bugs can move forward.
Assignee | ||
Comment 4•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=1ac25dd383614a47ecec807676456cc2abf46a76
Assignee | ||
Comment 5•7 years ago
|
||
Assignee | ||
Updated•7 years ago
|
Whiteboard: dom-ce-m2
Assignee | ||
Comment 7•7 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=947ae332681ac40b36879a177f29279c1b1d9300&filter-tier=1&group_state=expanded&selectedJob=97885634
Assignee | ||
Comment 8•7 years ago
|
||
Comment on attachment 8866161 [details] [diff] [review] Patch, v3 Review of attachment 8866161 [details] [diff] [review]: ----------------------------------------------------------------- Bug 1347446 makes accessing ElementReactionQueue becomes a bit non-trival (have to get it via DocGroup). Since bug 1359346 already refactors the creation time of CustomElementData, ReactionQueue can also be put into CustomElementData, then we can just get ReactionQueue from Element. May I have your review, William? Thank you.
Attachment #8866161 -
Flags: review?(wchen)
Updated•7 years ago
|
Attachment #8866161 -
Flags: review?(wchen) → review+
Pushed by echen@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/36f9b151741b Put the reaction queue in CustomElementData structure instead of using a map; r=wchen
Comment 10•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/36f9b151741b
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•