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

Clarify the usage the output I/O queues in the hooks #230

Merged
merged 2 commits into from
Sep 21, 2020
Merged

Clarify the usage the output I/O queues in the hooks #230

merged 2 commits into from
Sep 21, 2020

Conversation

andreubotella
Copy link
Member

@andreubotella andreubotella commented Sep 17, 2020

An "output" parameter was added to the hooks for standards in #215, but no explanation was given as to why it was needed. This change adds that clarification.


Preview | Diff

An "output" parameter was added to the hooks for standards in
#215, but no explanation was given as to why it was
needed. This change adds that clarification.
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

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

Thanks, looks good modulo nit. This isn't editorial per https://github.com/whatwg/meta/blob/master/COMMITTING.md. I do wonder if we should have something for these kind of changes as most folks would probably want to skip them too.

encoding.bs Outdated Show resolved Hide resolved
@andreubotella andreubotella changed the title Editorial: Clarify the usage the output I/O queues in the hooks Clarify the usage the output I/O queues in the hooks Sep 21, 2020
@andreubotella
Copy link
Member Author

In that case I've misunderstood what editorial means all along! 😅

Feel free to change the commit message when merging, then.

Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

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

Thanks! I think I'd like to wait with landing until we fix building as it wouldn't end up synchronized with the server anyway.

sideshowbarker added a commit to validator/validator that referenced this pull request Sep 21, 2020
This change is a hack to work around the fact the CSS-checking backend
doesn’t yet have support for the color-scheme property — and it’s not
clear that it should have such support at this point, because the
color-scheme property isn’t actually supported yet in any engine other
than Blink. So for now, this change causes the checker to filter out
(drop/ignore/suppress) any error messages about `color-scheme` values.

Related to whatwg/encoding#230
Related to whatwg/meta#188
Related to w3c/css-validator#285
@annevk annevk merged commit 3e16fb3 into whatwg:master Sep 21, 2020
@andreubotella andreubotella deleted the clarify-output-param branch September 21, 2020 14:14
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.

2 participants