- From: Florian Bösch <pyalot@gmail.com>
- Date: Fri, 18 May 2018 21:10:17 +0200
- To: Tom Ritter <tom@ritter.vg>
- Cc: Léonie Watson <tink@tink.uk>, Webapps WG <public-webapps@w3.org>
Received on Friday, 18 May 2018 19:10:43 UTC
On Fri, May 18, 2018 at 8:41 PM, Tom Ritter <tom@ritter.vg> wrote: > How is this exposed in other browsers? It seems like it would be > advantageous to require this string to _not_ contain uniquely > identifying information and to Non-normatively suggest an algorithm to > do so. > In order to provide reasonable defaults for the variety of controllers there are, a developer needs to know what controllers a user is using. The alternative is having malfitting defaults and requiring users to rebind functions manually to suit their controller, or pick a configuration scheme for a controller from a list, both of which are substantially worse UX for things that "should just work" and which native applications can "make just work". If you keep making it harder to compete with native applications UX, it's to little of anybodies surprise that web applications can't compete with native applications. duh.
Received on Friday, 18 May 2018 19:10:43 UTC