Consider unconditionally supporting `wrappedJSObject` on wrapped JS objects

RESOLVED FIXED in Firefox 67

Status

()

enhancement
P3
normal
RESOLVED FIXED
5 months ago
5 months ago

People

(Reporter: Nika, Assigned: Nika)

Tracking

unspecified
mozilla67
Points:
---

Firefox Tracking Flags

(firefox67 fixed)

Details

Attachments

(1 attachment)

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: nobody → nika
Priority: -- → P2
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
Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
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.