- From: Tom Ritter <tom@ritter.vg>
- Date: Fri, 18 May 2018 14:27:00 -0500
- To: Florian Bösch <pyalot@gmail.com>
- Cc: Léonie Watson <tink@tink.uk>, Webapps WG <public-webapps@w3.org>
On 18 May 2018 at 14:10, Florian Bösch <pyalot@gmail.com> wrote: > 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. What? How is saying "Playstation Controller Model 4" not indicating what controller a user is using, and how is not saying "Playstation Controller Model 4 Serial 28464927495" making the web ecosystem worse than the native applications? -tom
Received on Friday, 18 May 2018 19:27:53 UTC