Closed
Bug 1189822
Opened 9 years ago
Closed 8 years ago
Remove RegisterDOMExpandoObject and associated machinery
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla55
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
3.06 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
4.66 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
8.61 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
2.62 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
4.38 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
Right now the only way to do the preservation is to create the expando, as far as I can tell.
Assignee | ||
Updated•8 years ago
|
Summary: Consider having a way to preserve the wrapper for a DOM proxy without forcing creation of an expando object → Remove RegisterDOMExpandoObject and associated machinery
Assignee | ||
Comment 1•8 years ago
|
||
Attachment #8866136 -
Flags: review?(peterv)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•8 years ago
|
||
Attachment #8866137 -
Flags: review?(peterv)
Assignee | ||
Comment 3•8 years ago
|
||
Attachment #8866138 -
Flags: review?(peterv)
Assignee | ||
Comment 4•8 years ago
|
||
This is something that should have happened in bug 1352430 but was missed there.
Attachment #8866139 -
Flags: review?(peterv)
Assignee | ||
Comment 5•8 years ago
|
||
All DOMProxyHandler::ClearExternalRefsForWrapperRelease now does is clear a backpointer to the expando, and that's handled during reflector finalization already.
Attachment #8866140 -
Flags: review?(peterv)
Updated•8 years ago
|
Attachment #8866136 -
Flags: review?(peterv) → review+
Updated•8 years ago
|
Attachment #8866137 -
Flags: review?(peterv) → review+
Updated•8 years ago
|
Attachment #8866138 -
Flags: review?(peterv) → review+
Updated•8 years ago
|
Attachment #8866139 -
Flags: review?(peterv) → review+
Updated•8 years ago
|
Attachment #8866140 -
Flags: review?(peterv) → review+
Pushed by bzbarsky@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/810a380512e9
part 1. Switch DOMProxyHandler::EnsureExpandoObject to using normal wrapper preservation instead of RegisterDOMExpandoObject. r=peterv
https://hg.mozilla.org/integration/mozilla-inbound/rev/d820067e4d5f
part 2. Remove the DOM proxy expando object hashtable in xpconnect. r=peterv
https://hg.mozilla.org/integration/mozilla-inbound/rev/5ccd27cf7166
part 3. Stop using EnsureExpandoObject in codegen code when we just want to preserver the wrapper for a DOM proxy. r=peterv
https://hg.mozilla.org/integration/mozilla-inbound/rev/793ab87511f5
part 4. Fix finalization for DOM overridebuildins proxies to not clear the expando if it's for a different reflector. r=peterv, sfink
https://hg.mozilla.org/integration/mozilla-inbound/rev/30f6ea5ad9e6
part 5. Remove the now-unnecessary DOMProxyHandler::ClearExternalRefsForWrapperRelease function. r=peterv
Comment 7•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/810a380512e9
https://hg.mozilla.org/mozilla-central/rev/d820067e4d5f
https://hg.mozilla.org/mozilla-central/rev/5ccd27cf7166
https://hg.mozilla.org/mozilla-central/rev/793ab87511f5
https://hg.mozilla.org/mozilla-central/rev/30f6ea5ad9e6
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•