- From: dontcallmedom-bot <notifications@github.com>
- Date: Mon, 09 Sep 2024 03:09:38 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 9 September 2024 10:09:41 UTC
While crawling [Fullscreen API Standard](https://fullscreen.spec.whatwg.org/), 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 [requestFullscreen(options)](https://fullscreen.spec.whatwg.org/#dom-element-requestfullscreen) algorithm resolves/rejects a promise directly in a step that runs in parallel * [ ] The [exit fullscreen](https://fullscreen.spec.whatwg.org/#exit-fullscreen) 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> -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/issues/240 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fullscreen/issues/240@github.com>
Received on Monday, 9 September 2024 10:09:41 UTC