Get rid of NS_ERROR_TYPE_ERR
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: emk, Assigned: bzbarsky)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
| Reporter | ||
Updated•12 years ago
|
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Updated•7 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 3•6 years ago
|
||
I filed bug 1581172 on NS_ERROR_DOM_TYPE_ERR.
| Assignee | ||
Comment 4•6 years ago
|
||
The only ways DispatchReceivedData can fail are if our scope is torn down, we
OOM when creating a typed array, or we fail to queue a runnable. These all
seem like pretty unexpected situations, so NS_ERROR_UNEXPECTED seems
appropriate if we don't want to just propagate through the error from
DispatchReceivedData.
| Assignee | ||
Comment 5•6 years ago
|
||
The actual return code we return here doesn't really matter, since there is
already an exception on the JSContext. NS_ERROR_UNEXPECTED is as good as
anything, since we don't expect bogus options.
| Assignee | ||
Comment 6•6 years ago
|
||
NS_ERROR_DOM_TYPE_ERR is not much better, but this at least allows us to get
rid of NS_ERROR_TYPE_ERR completely...
Updated•6 years ago
|
Comment 8•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/578478de9488
https://hg.mozilla.org/mozilla-central/rev/857146a2bb00
https://hg.mozilla.org/mozilla-central/rev/93327435846a
Description
•