W3C home > Mailing lists > Public > public-device-apis@w3.org > January 2016

Re: [vibration] Returning false if vibration hardware is not present?

From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
Date: Tue, 26 Jan 2016 08:17:58 +0000
To: Philip Rogers <pdr@chromium.org>, Frederick Hirsch <w3c@fjhirsch.com>
CC: Nick Doty <npdoty@ischool.berkeley.edu>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <F630ED85-FEEA-4771-B1C8-6C1D4D2A8EF9@intel.com>

> On 26 Jan 2016, at 02:47, Philip Rogers <pdr@chromium.org> wrote:
> 
> I've filed this as a bug against Chromium. If you'd like to follow along, star https://code.google.com/p/chromium/issues/detail?id=579628.

Thanks -- you got one more star from me :-)

> It may make sense to explicitly call this usecase out in the spec. The ambiguous language makes this difficult to rely on.

Good idea.

Frederick - I guess we should add this informative clarification to the errata? However, there lies a practical issue that not everyone looks at errata. Could we also update the Editor's Draft to match, perhaps rename it to "Level 2" or such?

> Taking off my browser dev hat and putting on my web developer hat... On my site, given the current language of the spec, I have no option but to detect desktop browsers and show a warning for them. This doesn't work for devices like the Nexus 7 without vibration hardware, but it covers the common case since most mobile devices have vibration hardware.

Seems like a reasonable UX.

If the feature is considered progressive enhancement by web developers there should be no issue. For those use cases that have this feature on the critical path, should inform the user that the UX could compromised on devices that do not support the feature.

Thanks,

-Anssi
Received on Tuesday, 26 January 2016 08:18:39 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:07 UTC