Incorrect analogy of promise chains resembling a stack in documentation

[Maddily]

MDN URL

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise

What specific section or headline is this issue about?

Chained Promises

What information was incorrect, unhelpful, or incomplete?

The documentation on the MDN page Promise uses an analogy to describe the behavior of promise chains: "The promises of a chain are nested in one another, but get popped like the top of a stack. The first promise in the chain is most deeply nested and is the first to pop." This analogy is misleading because it inaccurately describes the order in which promises are resolved. A stack follows a Last In, First Out (LIFO) order, while promises in a chain are resolved in a First In, First Out (FIFO) order, more like a queue.

What did you expect to see?

I expected to see a description that accurately reflects the sequential nature of promise chains. A correct explanation would clarify that promises in a chain are executed in the order they are created, with each promise waiting for the previous one to resolve.

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

Suggested Revision:

The promises in a chain are executed in sequence, where each promise waits for the previous one to resolve before continuing. The first promise in the chain is the first to be resolved, and subsequent promises are resolved in the order they appear in the chain.

MDN metadata

Page report details

• Folder: en-us/web/javascript/reference/global_objects/promise
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise
• GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/javascript/reference/global_objects/promise/index.md
• Last commit: 10b3423
• Document last modified: 2023-11-29T09:09:55.000Z

[Ashish-CodeJourney]

Raised a PR for the same
#33790

Please review, suggestions will be appriciated

[Maddily]

Thank you everyone for your work on this issue and for the improvements made to the documentation. The changes address the concerns I raised and provide a much clearer explanation. I appreciate the effort put into this.

I'm closing this issue now. Thanks again!