[w3c/screen-orientation] "reject and nullify the current lock promise" and tasks (Issue #234) from Anne van Kesteren on 2022-10-27 (public-webapps-github@w3.org from October 2022)

From: Anne van Kesteren <notifications@github.com>
Date: Thu, 27 Oct 2022 05:33:20 -0700
To: w3c/screen-orientation <screen-orientation@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/screen-orientation/issues/234@github.com>

I don't really understand why this queues tasks, until I saw that it also had an "in parallel" caller. However, that caller should probably queue a task to run this as this algorithm inspects document state that's not going to be available in parallel, right?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/screen-orientation/issues/234
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/screen-orientation/issues/234@github.com>

Received on Thursday, 27 October 2022 12:33:32 UTC