- From: Jeffrey Yasskin <notifications@github.com>
- Date: Mon, 29 Aug 2016 11:41:03 -0700
- To: w3c/permissions <permissions@noreply.github.com>
Received on Monday, 29 August 2016 18:42:07 UTC
Taking [`enableHighAccuracy`](https://github.com/w3ctag/spec-reviews/blob/master/2015/03/Permissions.md#insufficient-reflection) as an example, there might be a difference in the prompt (UX) to express whether the page wants coarse or expensive results, and developers have to be aware of the `enableHighAccuracy` field in geolocation's `PermissionDescriptor` in order to use it. I think Bluetooth could get away with just `query("bluetooth")` by returning the full list of allowed `BluetoothDevice` objects, and making the developer filter them. That would be more difficult with Geolocation, MIDI, and Push, where the different levels of the API could be most combinations of `"granted"`, `"prompt"`, or `"denied"`. Bluetooth couldn't get away with just `request("bluetooth")`, because of the need to filter the prompt. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/42#issuecomment-243215147
Received on Monday, 29 August 2016 18:42:07 UTC