gecko-dev/dom/promise/tests
Boris Zbarsky a6fdc48869 Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley
These are cases that are implementing the "convert an exception to a Promise"
steps of the Web IDL spec.  Typically the exception is thrown in the current
compartment; the Promise returned should simply match that.  Otherwise we can
end up with a situation in which the promise doesn't actaully have access to
its rejection value, which will cause problems if someone uses then() on the
promise: the return value of the then() call will get a sanitized exception
instead of the real one.

We _could_ try to match the actual compartment of the exception, in theory.
But it's not clear why this would be preferable to using the current
compartment, even if there were cases in which the exception _doesn't_ match
the current compartment.  Which there likely are not.

MozReview-Commit-ID: Ac2BHIHxfvY

--HG--
rename : dom/promise/tests/test_promise_argument.html => dom/promise/tests/test_promise_retval.html
rename : dom/promise/tests/test_promise_argument_xrays.html => dom/promise/tests/test_promise_retval_xrays.html
2018-02-10 01:34:10 -05:00
..
unit Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian 2018-02-06 09:36:57 -08:00
chrome.ini Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
file_promise_and_timeout_ordering.js
file_promise_argument_tests.js Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
file_promise_retval_tests.js Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
file_promise_xrays.html
mochitest.ini Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
promise_uncatchable_exception.js
test_bug883683.html
test_on_new_promise.html Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian 2018-02-06 09:36:57 -08:00
test_on_promise_settled.html Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian 2018-02-06 09:36:57 -08:00
test_on_promise_settled_duplicates.html Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian 2018-02-06 09:36:57 -08:00
test_promise.html
test_promise_and_timeout_ordering.html
test_promise_and_timeout_ordering_workers.html
test_promise_argument.html
test_promise_argument_xrays.html Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
test_promise_callback_retval.html
test_promise_retval.html Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
test_promise_retval_xrays.html Bug 1436276. Bindings should create their return promises in the current compartment even when called over Xrays. r=bholley 2018-02-10 01:34:10 -05:00
test_promise_uncatchable_exception.html
test_promise_utils.html
test_promise_xrays.html
test_resolve.html
test_resolver_return_value.html
test_species_getter.html
test_thenable_vs_promise_ordering.html
test_webassembly_compile.html Bug 1347644 - Baldr: implement ConsumeStreamCallback in browser (r=bkelly) 2017-10-10 14:41:24 -05:00
test_webassembly_compile_sample.wasm Bug 1347644 - Baldr: implement ConsumeStreamCallback in browser (r=bkelly) 2017-10-10 14:41:24 -05:00
test_webassembly_compile_worker.js Bug 1347644 - Baldr: implement ConsumeStreamCallback in browser (r=bkelly) 2017-10-10 14:41:24 -05:00
test_webassembly_compile_worker_terminate.js Bug 1347644 - Baldr: implement ConsumeStreamCallback in browser (r=bkelly) 2017-10-10 14:41:24 -05:00