- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Apr 2015 07:21:05 +0000
- To: public-web-nfc@w3.org
anssiko has just created a new issue for https://github.com/w3c/web-nfc: == Does the visibilityState of the page have effect on the API behaviour? == How should the API behave if the [visibilityState](http://www.w3.org/TR/page-visibility/#dom-document-visibilitystate) of the page is hidden? This is currently unspecified, i.e. considered an implementation detail. Some existing APIs that make use of hardware devices such as [vibrate()](http://www.w3.org/TR/vibration/#dfn-processing-vibration-patterns) behave differently depending on the visibilityState of the page in order to make it obvious to the user which page is using the device. The [Security and Privacy doc](http://w3c.github.io/web-nfc/security-privacy.html) seems to suggest the API should be functional only if the page is visible to the user: > the user needs to be aware of exactly what a web page is intending to do with NFC at any given moment See https://github.com/w3c/web-nfc/issues/16
Received on Tuesday, 14 April 2015 07:21:17 UTC