- From: dontcallmedom-bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2025 10:31:44 +0000
- To: public-web-bluetooth-log@w3.org
dontcallmedom-bot has just created a new issue for https://github.com/WebBluetoothCG/web-bluetooth: == [web-bluetooth-scanning] Missing tasks in parallel steps in Web Bluetooth Scanning == While crawling [Web Bluetooth Scanning](https://webbluetoothcg.github.io/web-bluetooth/scanning.html), the following algorithms fire an event, or resolve or reject a Promise, within a step that runs [in parallel](https://html.spec.whatwg.org/multipage/infrastructure.html#in-parallel) without first queuing a task: * [ ] The [Bluetooth/requestLEScan(options)](https://webbluetoothcg.github.io/web-bluetooth/scanning.html#dom-bluetooth-requestlescan) algorithm resolves/rejects a promise directly in a step that runs in parallel See [Dealing with the event loop](https://html.spec.whatwg.org/multipage/webappapis.html#event-loop-for-spec-authors) in the HTML specification for guidance on how to deal with algorithm sections that run *in parallel*. <sub>Cc @dontcallmedom @tidoust</sub> <sub>This issue was detected and reported semi-automatically by [Strudy](https://github.com/w3c/strudy/) based on data collected in [webref](https://github.com/w3c/webref/).</sub> Please view or discuss this issue at https://github.com/WebBluetoothCG/web-bluetooth/issues/642 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 January 2025 10:31:45 UTC