Skip to content

Conversation

nicolo-ribaudo
Copy link
Member

I was reading through the web integration doc again, and changed some parts to highlight more the core design aspects and the reason behind them. Importantly, I added the same observations that there are in the slides for the upcoming TC39 meeting:

  • the proposed behavior matches what you would usually get from userland implementations
  • in many cases there is no difference between dispatch and causal contexts.

I also changed the note about Observers, marking that as Important using GitHub's syntax (https://github.com/orgs/community/discussions/16925), explaining why going through the always-empty-context path can be explained as coherent.

@nicolo-ribaudo
Copy link
Member Author

I pushed a new commit removing most of the mentions to the registration context. It was defined and referred to all over the document, but almost never actually used in a way that is meaningfully different from the dispatch context. We also don't really need to define the dispatch context anymore, since we don't define its opposite.

Co-authored-by: Andreu Botella <andreu@andreubotella.com>
Co-authored-by: Andreu Botella <andreu@andreubotella.com>
@legendecas legendecas merged commit ede485a into tc39:master Apr 11, 2025
5 checks passed
@nicolo-ribaudo nicolo-ribaudo deleted the clarify-web-integration branch April 11, 2025 13:00
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants