Could you maybe explain the mess and how returning a promise helps resolve it? At least to me one seems like an implementation concern we'd have to resolve one way or another and the other is a nicety of the API, but doesn't really change the implementation. Except it requires it to do something with the promise, but that seems strictly additional to having to deal with the race. (One way out might be to make `unlock()` no-op and require exiting fullscreen instead. Not sure how compatible that is though.) -- Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/issues/104#issuecomment-1275708870 You are receiving this because you are subscribed to this thread. Message ID: <w3c/screen-orientation/issues/104/1275708870@github.com>
Received on Wednesday, 12 October 2022 07:25:14 UTC