- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Aug 2024 17:23:08 +0000
- To: public-css-archive@w3.org
My argument for not customizing this is that it empowers the UA to provide all of these good behaviors to all popover hints rather than requiring each developer to think about them, e.g.: * Clear allowance to align with user / OS preferences, * Can be based on a time after stopping movement: https://github.com/w3c/csswg-drafts/issues/9236#issuecomment-2288821778, * Can eliminate or significantly reduce the delay for opening the n'th hint after a first one is open: based on discussion in https://github.com/w3c/csswg-drafts/issues/9236#issuecomment-2289285305, I also feel like the use cases for instant reveal are fundamentally different than a "short" delay, and may be best represented by either a different named concept, e.g. hover. > Some apps might want to have snappier values, others — more relaxed. I worry that this sort of customization may not actually be providing a better user experience. There were some questions during the call about touch - I think that just like click, contextmenu, :hover, and other "mouse-centric" properties where we already have a way to trigger with touch, we would do the same for this capability. My proposal which aligns with android behavior would be to show it after a short delay of pressing down - long enough to not be considered a click. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9236#issuecomment-2289395680 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 August 2024 17:23:09 UTC