- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Sep 2019 22:23:48 +0000
- To: public-css-archive@w3.org
> Actually, I think this is more useful if it does focus on the presence of an actual visible button, or to generalize that slightly, an "obvious user-agent-supplied control for navigating back", as opposed to a "hidden" control such as a swipe gesture or keyboard shortcut. As I elaborated a bit, I think if the gesture is a natural, widely-known thing that you can expect users to know exists and use, then it would suffice for the purpose of this MQ - you don't need to provide your own in-app Back functionality. But that's definitely not true on Android devices, and I'm not familiar enough with iOS ones to know if their swiping does indeed meet those (rather stringent) requirements. But yeah, I agree that things like keyboard shortcuts do not meet this bar. (I *personally* use Alt+Left as my primary Back mechanism when on a keyboard, but I know I'm a tiny minority.) > Ultimately, it would be at the discretion of the user agent to determine what "obvious" and "non-obvious" means, but the spec should give some examples (gestures, keyboard shortcuts and functionality inside drop-down menus would be "non-obvious"). Yes, sounds good. > Please credit me (mgiuca@ / Matt Giuca) too :) Since I was the original original proposer; @fallaciousreasoning converted it into a formal proposal to the CSSWG. Will do. ^_^ -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4187#issuecomment-528614290 using your GitHub account
Received on Thursday, 5 September 2019 22:23:50 UTC