Closed
Bug 1188612
Opened 10 years ago
Closed 10 years ago
Transferable errors should become NS_DOM_DATA_CLONE_ERR, not built-in spidermonkey errors.
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla43
Tracking | Status | |
---|---|---|
firefox43 | --- | fixed |
People
(Reporter: khuey, Assigned: baku)
References
Details
Attachments
(1 file)
10.18 KB,
patch
|
sfink
:
review+
|
Details | Diff | Splinter Review |
webmessaging/postMessage_dup_transfer_objects.htm tests that doing postMessage("blah", [foo, foo]); throws an NS_ERROR_DOM_DATA_CLONE_ERR. Today it throws a builtin spidermonkey error. There are a few parts to this:
1. We need to change the js engine to always call the error hook (in other words we need to ReportErrorTransferable for JSMSG_SC_DUP_TRANSFERABLE).
2. We need to change PostMessageEvent (and other structured clone callers) to actually use the error hook.
3. We need to test that the other ways that transferables can fail also get an NS_ERROR_DOM_DATA_CLONE_ERR.
Comment 1•10 years ago
|
||
I think baku is fixing 2 and 3 in one of his "make structured clone handling sane" bugs.
Assignee | ||
Comment 3•10 years ago
|
||
Attachment #8640499 -
Flags: review?(sphink)
Updated•10 years ago
|
Attachment #8640499 -
Flags: review?(sphink) → review+
Comment 5•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox43:
--- → fixed
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•