Skip to content

in parallel #168 #180

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

Merged
merged 1 commit into from
May 5, 2017
Merged

in parallel #168 #180

merged 1 commit into from
May 5, 2017

Conversation

plehegar
Copy link
Member

@plehegar plehegar commented Mar 3, 2017

No description provided.

@jimsch
Copy link
Contributor

jimsch commented Mar 3, 2017

I would not recommend this be adopted even if the document were open. In parallel implies to me at the same time, in fact it will generally be performed at a different time so asynchronously (which allows in parallel) is a better term

@sleevi
Copy link
Contributor

sleevi commented Mar 22, 2017

@jimsch This is a defined term as part of the HTML Infrastructure that specifically provides guidance contrary to your interpretation.

https://www.w3.org/TR/html/infrastructure.html#in-parallel covers that.

Having examined this PR, +1 to supporting it

@plehegar
Copy link
Member Author

plehegar commented May 5, 2017

@mwatson2 any stopper in merging this?

@mwatson2
Copy link
Collaborator

mwatson2 commented May 5, 2017

Looks good to me.

@plehegar plehegar merged commit 667021e into master May 5, 2017
@plehegar plehegar deleted the in-parallel branch May 5, 2017 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants