- From: Mike Wasserman <notifications@github.com>
- Date: Tue, 09 May 2023 17:02:26 -0700
- To: w3c/screen-orientation <screen-orientation@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 10 May 2023 00:02:32 UTC
This seems like it would be a clear win for screen orientation API ergonomics, but I'm curious about the premise: `The above assumption is wrong, because .unlock() IPC SHOULD notify of success/failure.` Can you reference source material regarding how underlying OS APIs report the success or failure of these requests? I'm a novice in this space and I don't see anything quite so obvious. It doesn't help that Chromium's current implementation seems incautious at first glance. After issuing OS requests, promises seem to be resolved immediately for locks matching the current orientation, or when a matching orientation change event occurs. Should the spec incorporate potentially undetectable OS API failures, beyond leaving promises indefinitely unresolved? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/issues/104#issuecomment-1541037869 You are receiving this because you are subscribed to this thread. Message ID: <w3c/screen-orientation/issues/104/1541037869@github.com>
Received on Wednesday, 10 May 2023 00:02:32 UTC