- From: Reilly Grant via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Oct 2020 18:19:52 +0000
- To: public-web-bluetooth-log@w3.org
reillyeon has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth: == Should there be a scanning stopped event? == Both [watchAdvertisements()](https://webbluetoothcg.github.io/web-bluetooth/#dom-bluetoothdevice-watchadvertisements) and [requestLEScan()](https://webbluetoothcg.github.io/web-bluetooth/scanning.html#dom-bluetooth-requestlescan) require that the document be [fully active](https://html.spec.whatwg.org/multipage/browsers.html#fully-active) and will abort the scan if full activity is lost. This is in contrast to APIs such as [[SENSORS]](https://w3c.github.io/sensors/) which also require a fully active document but will resume events for sensor changes when the document becomes visible or [[SCREEN-WAKE-LOCK]](https://w3c.github.io/screen-wake-lock/) which will fire an event when a wake lock is released due to loss of visibility. This question of how to handle pausing the WebNFC API on loss of full activity [was raised](https://docs.google.com/document/d/11otkoYp1_T-_sZJ0E1wY8OwDUdXbXZ3NHzxPgl38pwE/edit#heading=h.x1yysvgfn3av) at the TPAC 2020 meeting of the WICG and Bluetooth's behavior was flagged as suboptimal compared to other APIs. Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/527 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 October 2020 18:19:54 UTC