[mediaqueries-4] add example of 'pointer: none' to table, add note about how UA could determine "primary" input #739
Conversation
- add classic `pointer: none` inputs - preferred term is digitizers, rather than screens (e.g. Wacom are external devices, not screens) - advanced stylus digitizers can sense a hovering stylus, and do trigger hover interactions - split out basic and advanced stylus - removed the `<col>` ... appears to serve no actual (styling?) purpose
- adds an introductory paragraph in the main "Interaction Media Features" section that introduces the concept of primary/all input mechanisms - based on the conversation in w3c#690, add a (non normative) note hinting at ways in which UAs can potentially determine what is and isn't primary
9d09d39 to
d891221
Compare
|
👍 overall. My only request is that you wrap the lines in a similar fashion to the rest of the spec? We use semantic linebreaking, so just breaking on commas and periods is usually all you need to do. |
|
Never mind, forgot I can take care of that myself now. Merging, thanks! |
|
Lovely, thanks |
|
Thanks @patrickhlauke for submitting the PR, and @tabatkins for merging it. For the record, I fully agree with this PR. Given that @patrickhlauke and I have had our fair share of disagreement on this general area, I want to come clear that this is something we do agree on. |
|
Oh, absolutely @frivoal. And I hope our disagreements are seen in the right context...nothing personal, just that we seem to be coming at this from different angles/with different use cases. I'm all for finding some shared middle ground :) |
expands the table https://drafts.csswg.org/mediaqueries/#mf-interaction to include an example of
pointer:none, swaps "stylus-based screen" to "stylus digitizer" (preferred/common term), adds distinction between basic and advanced stylus (the latter does support hover)adds an introductory paragraph in the main "Interaction Media Features" section that introduces the concept of primary/all input mechanisms
based on the conversation in [mediaqueries-4] Interaction Media Features make a rigid primary/"rare" distinction #690 (comment), add a (non normative) note hinting at ways in which UAs can potentially determine what is and isn't primary (based on @frivoal's explanation to me in that thread about what the expectation for UAs seems to be...this makes it a bit more explicit)
both these changes should be editorial, rather than substantive, as they don't introduce any new normative requirements.
this addition would, as far as i'm currently concerned, close #690