If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Handle callbacks that are not nullable correctly

RESOLVED FIXED

Status

()

Core
DOM
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: bz, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

This applies to callbacks (not callback interfaces).  Right now both unwrapping and wrapping assume nullability without failing codegen if it's not present.  We should fix that.
Unwrapping got addressed in bug 792137.

Not sure how much we care about wrapping.  The obvious change to wrapping would be to use ObjectValue() when not nullable, but I'm not sure there's a win to be had there over using ObjectOrNullValue() no matter what.
Depends on: 792137
Once I land bug 779048, we'll see what remains to be done here.
Depends on: 779048
This is fully fixed now, with a null-check on the CallbackFunction* and everything, in bug 779048.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.