> Okay, so the promise gives web developers a chance to do things better, Not only that, but predictability and a degree of assurance that unlocking actually happened (or, in an exceptional case, not). > but we still have to define what happens when they don't. Yes, absolutely: that's mostly what all the machinery that aborts the promises of previous calls to `lock()` across all associated documents does. The current model is far from perfect (how it works with events is still a bit busted as per #184), but it's workable enough. > It seems weird for IPC to go out-of-order but I guess it depends on what it ends up talking to. Yeah, this is why the integration with FS API should really help: it will prevent much of the weirdness that can happen when trying to full screen and then change orientation by allowing the user agent to do it all smoothly in one action. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/issues/104#issuecomment-1277317555 You are receiving this because you are subscribed to this thread. Message ID: <w3c/screen-orientation/issues/104/1277317555@github.com>
Received on Thursday, 13 October 2022 09:34:49 UTC