W3C home > Mailing lists > Public > public-device-apis-log@w3.org > May 2017

Re: [sensors] Add 'user triggered activation' as mitigation strategy

From: Alexander Shalamov via GitHub <sysbot+gh@w3.org>
Date: Mon, 22 May 2017 16:37:16 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-303153460-1495471035-sysbot+gh@w3.org>
`The following code will only work in browsers that don't implement this.`

The fact that start() is called from event handler, has no IOP implications, webdev can call start() from onload if needed. Both cases will work as long as engine supports EventTarget interface.

However, when event handler is associated with interactive element, UA may use this information as  one of the criteria to e.g., prompt user or auto-grant permission. Since the UI, prompting or enforcement of mitigation strategies is optional and left up to the UA [5.4.1](https://w3c.github.io/sensors/#permissions) or [5.2](https://w3c.github.io/sensors/#mitigation-strategies-case-by-case), I don't see how this PR might introduce IOP. You can't break API contract if it says 'may'.

Do you have any other examples?

GitHub Notification of comment by alexshalamov
Please view or discuss this issue at https://github.com/w3c/sensors/pull/207#issuecomment-303153460 using your GitHub account
Received on Monday, 22 May 2017 16:37:24 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:54 UTC