Skip to content

Tweak AsyncContext propagation for events to mention affecting in-flight actions#154

Open
nicolo-ribaudo wants to merge 1 commit into
masterfrom
nicolo-ribaudo-patch-1
Open

Tweak AsyncContext propagation for events to mention affecting in-flight actions#154
nicolo-ribaudo wants to merge 1 commit into
masterfrom
nicolo-ribaudo-patch-1

Conversation

@nicolo-ribaudo
Copy link
Copy Markdown
Member

  • Mention the example of a video, where pause/play may affect an in-progress load
  • Explicitly mention that even though DOM adoption does not follow from the principle, it's something that we intend to cover
  • Change the wording about APIs that create an object to not require the object to be returned, so that it covers the .innerHTML case.

Comment thread WEB-INTEGRATION.md

Asynchronous APIs that fire events as a result of either:
- some method/setter call, for which the event is fired either (a) on the object returned by the method (either directly or wrapped in a promise), or (b) if the instance is not a singleton on the object whose method was called on, would propagate the context;
- some method/setter call, for which the event is fired either (a) on the object created by the method, or (b) if the instance is not a singleton on the object whose method was called on, would propagate the context;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- some method/setter call, for which the event is fired either (a) on the object created by the method, or (b) if the instance is not a singleton on the object whose method was called on, would propagate the context;
- some method/setter call, for which the event is fired either (a) on an object created by the method, or (b) if the instance is not a singleton on the object whose method was called on, would propagate the context;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants