Closed
Bug 1372390
Opened 7 years ago
Closed 4 years ago
Promise.all returns already-resolved promises for any combination of non-promises and resolved promises.
Categories
(Developer Documentation Graveyard :: JavaScript, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: trusktr, Unassigned)
References
()
Details
:: Developer Documentation Request Request Type: Correction Gecko Version: unspecified Technical Contact: :: Details The docs say if Promise.all receives an array of non-promises, it will return an unresolved promise. However, Chrome returns a resolved promise. If all items in the array are any mix of non-promises and resolved promises, or an empty array, then Chrome always returns an already-resolved promise. Should the docs be corrected? Is Firefox behavior different? Here's the section I'm referring to: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all#Asynchronicity_or_synchronicity_of_Promise.all
Comment 1•4 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•