Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify which event loop to use for posting messages #4917

Merged
merged 2 commits into from
Sep 28, 2019

Conversation

domenic
Copy link
Member

@domenic domenic commented Sep 18, 2019

source Outdated
@@ -98334,7 +98334,8 @@ function receiver(e) {
any exceptions.</p></li>

<li>
<p><span>Queue a task</span> on the <span>posted message task source</span> to run the
<p><span>Queue a task</span> on the <span>posted message task source</span> of
Copy link
Member

Choose a reason for hiding this comment

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

Given that we mention it here and this is the only task queueing, we can maybe remove "The task source for the tasks in cross-document messaging is the posted message task source." and inline the <dfn>?

@@ -99178,7 +99179,8 @@ interface <dfn>BroadcastChannel</dfn> : <span>EventTarget</span> {

<li>
<p>For each <code>BroadcastChannel</code> object <var>destination</var> in
<var>destinations</var>, <span>queue a task</span> that runs the following steps:</p>
<var>destinations</var>, <span>queue a task</span> on <var>destination</var>'s <span>relevant
Copy link
Member

Choose a reason for hiding this comment

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

What task source does this use? (Note that this section is parallel to the one that defines the "posted message task source" and so while that might be a good choice, it doesn't appear in scope.)

Copy link
Member Author

Choose a reason for hiding this comment

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

A few lines below it says DOM manipulation task source. I'll inline that in to the call site.

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

Successfully merging this pull request may close these issues.

'Window post message steps' doesn't define which event loop is used for queuing a task
2 participants