Граф коммитов

4 Коммитов

Автор SHA1 Сообщение Дата
Victor Porof 0a8ff0ad85 Bug 1561435 - Format dom/, a=automatic-formatting
# ignore-this-changeset

Differential Revision: https://phabricator.services.mozilla.com/D35951

--HG--
extra : source : 62f3501af4bc1c0bd1ee1977a28aee04706a6663
2019-07-05 10:44:55 +02:00
Alec Gibson 6a56241703 Bug 1532935 - Enable ESLint for dom/promise (manual changes). r=mccr8
Patch by Alec, updated by Standard8.

Differential Revision: https://phabricator.services.mozilla.com/D29646

--HG--
extra : moz-landing-system : lando
2019-06-25 20:12:47 +00:00
Alec Gibson 6614404241 Bug 1532935 - Enable ESLint for dom/promise (automatic changes). r=mccr8
# ignore-this-changeset

Differential Revision: https://phabricator.services.mozilla.com/D29645

--HG--
extra : moz-landing-system : lando
2019-06-25 20:11:52 +00:00
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