Skip to content

[mediaqueries-4] Move 'pointer'/'hover' note, reword "can potentially" to "should strongly consider" #2470

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
Mar 24, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions mediaqueries-4/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -1752,7 +1752,14 @@ Note: the '@media/hover', '@media/any-hover', '@media/pointer', and '@media/any-
or the complete absence, of pointing devices,
and can not be used to detect the presence of non-pointing device input mechanisms such as keyboards.
Authors should take into account the potential presence of non-pointing device inputs,
regardless of which values are matched when querying these features.
regardless of which values are matched when querying these features.

<div class="note">
While 'pointer' and 'hover' can be used to design the main style and interaction
mode of the page to suit the primary input mechanism (based on the characteristics, or complete absence,
of the primary pointing device), authors should strongly consider using 'any-pointer' and 'any-hover'
to take into account all possible types of pointing devices that have been detected.
</div>

<h3 id="pointer">
Pointing Device Quality: the 'pointer' feature</h3>
Expand Down Expand Up @@ -1952,12 +1959,6 @@ Note: This feature is at risk.
</div>

<div class="note">
While 'pointer' and 'hover' can be used to design the main style and interaction
mode of the page to suit the primary input mechanism (based on the characteristics, or complete absence,
of the primary pointing device), 'any-pointer' and 'any-hover'
can be used to potentially take into account all possible types of pointing devices
that have been detected.

Designing a page that relies on hovering or accurate pointing
only because 'any-hover' or 'any-pointer' indicate that at least one of the available
input mechanisms has these capabilities is likely to result in a poor experience.
Expand Down