Closed
Bug 1528383
Opened 6 years ago
Closed 6 years ago
Consider unconditionally supporting `wrappedJSObject` on wrapped JS objects
Categories
(Core :: XPConnect, enhancement, P3)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
mozilla67
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Right now XPCOM objects implemented in JS need to explicitly write this.wrappedJSObject = this; in their ctor to support .wrappedJSObject on their wrapped object. It might be nice for ergonomics of using some APIs, especially those taking and returning nsISupports, to simply always support that getter.
|
Assignee | |
Comment 1•6 years ago
|
||
|
||
Updated•6 years ago
|
Assignee: nobody → nika
Priority: -- → P2
|
|
Assignee | |
Updated•6 years ago
|
Priority: P2 → P3
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8e58294baf24
Allow getting 'wrappedJSObject' without the attribute being defined, r=bholley
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
|
||
Comment 4•6 years ago
|
||
https://hg.mozilla.org/projects/oak/rev/8e58294baf24a304a10a1ac46607abc7711ad0a3
Bug 1528383 - Allow getting 'wrappedJSObject' without the attribute being defined, r=bholley
You need to log in
before you can comment on or make changes to this bug.
Description
•