- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 May 2017 17:21:48 +0000
- To: public-css-archive@w3.org
@patrickhlauke in the log above, pushing the scripting MQs to L5 is not related to this issue. Other than that, the WG felt that the use cases for being able to detect mixed hover and non-hover capable pointers were not compelling enough to justify the complexity needed to make that work, and decided to close this issue as no change. However, recognizing that the whole set of pointer/any-pointer/hover/any-hover was not the part of the spec we're most confident it, and that it is possible that as implementations come in contact with reality or as we learn more about use cases, we may still need to adjust, we marked them at risk. That way, if need be, we can pull them to level 5 to tweak them some more without slowing down the rest of the spec. Since this is a rejection of this issue you raised, I realize this is not the conclusion you were hoping for, but is this a conclusion you are willing to live with? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/841#issuecomment-302162965 using your GitHub account
Received on Wednesday, 17 May 2017 17:21:55 UTC