For now this bug just serves as a tracking issue, because there are still some open questions in the proposal repository, which need to be resolved before we can actually try to ship this feature.

v8 seems to ship this now https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/TXMOAEC0AW4

We're passing the tests for this in Nightly. Let's ship it.

I'm a bit hesitant to ship this now, because then it'll end up in Firefox 78, which is an ESR release, so when TC39 reaches a decision on https://github.com/tc39/proposal-promise-any/issues/38, we may end up in a situation where our ESR release ships with an outdated implementation. Unless we're okay with that resp. we're okay with backporting the final approved Promise.any spec to ESR.

The logical assignment proposal has a similar issue, where TC39 still needs to reach a conclusion for an open spec report: https://github.com/tc39/proposal-logical-assignment/issues/23.

Since Firefox 78 doesn't go to release until June 30, I wonder if we can get both of these issues resolved in the next TC39 meeting taking place June 1-4. I see the logical assignment issue is already on the TC39 agenda. A discussion of Promise.any is also on the agenda, but for a different issue, so maybe we could add this issue as well.

78 will be in Beta at that point, meaning if we land both these features now, we have options for each:

• No spec change = let it ride to release 78
• Spec change = uplift change to beta 78, ride to release (assuming change isn't too big)
• Spec issue unresolved = assess risk of riding to 78 as-is possibly backporting changes to ESR (vs. uplifting a change to pref off in 78)

:yulia, thoughts on this plan from a TC39 perspective?

Depends on D76392

The previous changeset made a change to test262-update.py. This changeset is
the result of running the script, like this:

cd js/src/tests
python test262-update.py --revision 25c9e334d301944537215caba1d7f44319f3e0da

The revision is taken from the first line of js/src/tests/test262/GIT-INFO; the
purpose of specifying that revision is to run the script again using the same
input, so that the output reflects only changes to the script itself, not new
tests.

Depends on D76393

This is planned for discussion at the upcoming plenary. I will update after we come to a decision ( https://github.com/tc39/agendas/blob/master/2020/06.md)

Discussion in tc39/proposal-promise-any#38 indicates this has been resolved informally ahead of the plenary; blocking bug 1641355 adjusts our behavior accordingly.

Issue 38 has been discussed by the committee, and will be resolved by https://github.com/tc39/proposal-promise-any/pull/64, which should allow us to move forward.

There is an overarching concern that hasn't been addressed yet but won't affect our work here.

Backed out for mochitest failures on test_xrayToJS.xhtml

Backout link: https://hg.mozilla.org/integration/autoland/rev/361a5a7112a3e1750fe71205f08d593861454e31
Log link: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=306383216&repo=autoland&lineNumber=6980

https://hg.mozilla.org/mozilla-central/rev/e9ae34f20fbe
https://hg.mozilla.org/mozilla-central/rev/0b491b101124

Compat data update: https://github.com/mdn/browser-compat-data/pull/6352
Release notes: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/79#JavaScript
Docs: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/any