Closed
Bug 1755387
Opened 4 years ago
Closed 4 years ago
Allow subclassing WebAssembly.Exception
Categories
(Core :: JavaScript: WebAssembly, defect, P3)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
99 Branch
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | fixed |
People
(Reporter: rhunt, Assigned: rhunt)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This requires looking up the prototype correctly in WasmExceptionObject::construct.
|
Assignee | |
Comment 1•4 years ago
|
||
Drive-by fix to avoid getting a potentially non-existent prototype for
WebAssembly.Tag in Module::instantiateTags when there are no tags
defined.
|
||
Updated•4 years ago
|
Severity: -- → S3
Pushed by rhunt@eqrion.net:
https://hg.mozilla.org/integration/autoland/rev/b92532ec1c11
wasm: Use the correct prototype when constructing WebAssembly.Exception. r=lth
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox99:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•