W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2020

[csswg-drafts] [css-mediaqueries-4] any-hover:none is slightly pointless in current implementation? (#5462)

From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
Date: Fri, 21 Aug 2020 21:35:04 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-683839262-1598045703-sysbot+gh@w3.org>
patrickhlauke has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-mediaqueries-4] any-hover:none is slightly pointless in current implementation? ==
Coming in very late on this, but as I'm currently rewriting an old article on the topic of interaction media features...

As currently defined, `any-hover:none` will only ever evaluate to true when *all* of the detected pointer inputs are not hover-capable. This makes the query fairly useless in practice. From a developer's point of view, I'd want to know "am I safe to rely on the user being able to hover, or are there *any* inputs that the user may jump to that don't support this?" - at least I'd want to check this far more often than "is it impossible for the user, using any of the inputs at their disposal, to trigger the hover" (the latter would be accomplished simply by checking `any-hover:hover` ... if *that* evaluates to false, I'd know that none of the inputs are hover capable).

Is it far too late in the day now to ask for the behaviour of `any-hover:none` to be amended? basically, changing this to behave similar to `any-pointer` which can have multiple values evaluating to true...and make this include `any-hover:none` (so *not* making that the "union" of all hover capabilities, as is currently the case).

/cc @frivoal

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5462 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 August 2020 21:35:06 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:13 UTC