-
Notifications
You must be signed in to change notification settings - Fork 159
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
"Default display mode" section is super confusing #1024
Comments
Consider this sentence (at the end of section 7.1):
If the user has overridden the manifest's display value, which way is the media feature supposed to go? Is this phrase deliberately not using the term "default display mode" to express some conceptual difference? If so, I can't what the difference is because both this sentence and the definition of "default display mode" rely on the term "apply". Relatedly, the definition of apply itself could use some help too: the definition says what it means to apply a manifest (when it "affects the presentation or behavior of a browsing context"), but it doesn't say what it means to apply a member of a manifest, though it gets used that way. Are all members considered to apply if the manifest as a whole applies, or to they only apply if they individually made some difference? Do they count as not applying if they've been overridden by the user? |
All good points (it's definitely confusing)... will see if we can come up with something better. Appreciate the suggestions and feedback 🙏. |
The concept of "default display mode" is very confusing. Is it the mode requested by the app manifest? The mode the UA would have defaulted to if there is no request from an app manifest? The display mode that is actually in effect at the end of the day?
It would be much easier to follow this section if there were two named concepts neither of which use the word "default":
(It also needs to be clarified whether the
display-mode
media query reflects the effective display mode, requested display mode, or something else.)The text was updated successfully, but these errors were encountered: