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

Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation. #949

Merged
merged 11 commits into from Feb 18, 2021

Conversation

dmurph
Copy link
Collaborator

@dmurph dmurph commented Jan 29, 2021

This change (choose at least one, delete ones that don't apply):

  • Makes editorial changes (changes informative sections, or changes normative sections without changing behavior)

Commit message:

Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation.

Person merging, please make sure that commits are squashed with one of the following as a commit message prefix:

  • editorial:

Preview | Diff

@dmurph dmurph requested a review from mgiuca January 29, 2021 23:05
@dmurph dmurph changed the title Display override editorial Editorial: Created explicit algorithm for choosing display mode, and add extension point for the display_override incubation. Jan 29, 2021
Copy link
Collaborator

@mgiuca mgiuca left a comment

Choose a reason for hiding this comment

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

lgtm with nits

index.html Outdated
mode</a>'s <a>fallback display mode</a>. This creates a fallback chain,
with the <a>default display mode</a> (<code>browser</code>) being the
last item in the chain.
The <dfn>fallback chain</dfn> for:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Historical note: The old text here was wrong (or rather, nonsensical):

If the user agent does support a fallback display mode, then it checks to see if it can use that display mode's fallback display mode.

This should have read "If the user agent does not support a given display mode, then it checks to see if it can use that display mode's fallback display mode."

This new text will help clarify it greatly. It might be worth adding a note to the commit message that this actually fixes broken text around how to deal with an unsupported display mode, even though we don't expect it to change implementations since we're preserving the intention behind the old broken text.

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
@dmurph dmurph merged commit 140001c into w3c:gh-pages Feb 18, 2021
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.

None yet

2 participants