Closed
Bug 1658946
Opened 5 years ago
Closed 5 years ago
Make resolving a promise with an XPCOM type more usable.
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
82 Branch
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | fixed |
People
(Reporter: emilio, Assigned: nika)
Details
Attachments
(1 file)
Right now stuff like this goes through this ToJSValue overload which doesn't pass an IID so it ends up causing us write code like this, which is not great. Ideally you wouldn't need the extra QueryInterface there if the interface is not ambiguous or if you pass a concrete interface type.
| Assignee | ||
Comment 1•5 years ago
|
||
This will allow resolving DOM promises with non-wrappercached XPIDL interfaces
in a more convenient manner, as the wrapped JS object will have more concrete
interface information without needing to invoke QueryInterface.
Updated•5 years ago
|
Assignee: nobody → nika
Status: NEW → ASSIGNED
Pushed by nlayzell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bed3d8831e0f
Wrap non-wrappercached interfaces more precisely in ToJSValue, r=peterv
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•