Re: [w3c/screen-orientation] Consume transient activation (PR #218) from Kagami Sascha Rosylight on 2022-10-27 (public-webapps-github@w3.org from October 2022)

From: Kagami Sascha Rosylight <notifications@github.com>
Date: Thu, 27 Oct 2022 02:51:08 -0700
To: w3c/screen-orientation <screen-orientation@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/screen-orientation/pull/218/c1293273443@github.com>

Oh, https://bugzilla.mozilla.org/show_bug.cgi?id=1767449 tracks that, thanks. Didn't know that!

Given that Fullscreen API does not consume the activation, I think this should have a telemetry so that we can know what websites will break when screen locking consumes it.

>I think it's rejecting the in Gecko because calling .lock() again inside the event handler is causing the AbortError to be returned (as the first promise hasn't settled).

Confirmed. Can we spec this instead? 😂

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/screen-orientation/pull/218#issuecomment-1293273443

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/screen-orientation/pull/218/c1293273443@github.com>

Received on Thursday, 27 October 2022 09:51:21 UTC