[mediaqueries-4] Change when any-* evaluate to 'none' #738
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A substantive spec/behavior change. Allowing any-hover:none and any-pointer:none to match when ANY of the available inputs are non-hover/non-pointer capable would allow authors to get a more holistic view of ALL available input methods to make - if they so wish - even more granular decisions about which functionality/style they wish to provide in their app/site
|
/cc @frivoal |
tabatkins
requested changes
Nov 22, 2016
|
Closing this, as I've come around to at least part of the reasoning (for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently,
any-pointer: noneandany-hover: noneonly evaluate to true when they apply to ALL pointers/input mechanisms. There are situations, however, where it would be useful if these evaluated to true if ANY pointers/input mechanisms had those characteristics. See the examples in this PR for use cases where this would be the case. This would clearly be a substantive change to the spec, but one that I feel would open up some more granular possibilities for authors.(this issue is a continuation of #715 which in turn came out of this isse #690)
Closes #737