Re: [w3c/screen-orientation] BREAKING CHANGE: unlock() returns a pormise (#183)

The thing is for all orientation locks, the UA can figure out whether we are already in an orientation that matches the lock or whether we should wait for a change. With `unlock()` or `default`, the UA would need to know what is the system lock (in most cases, when the manifest has an orientation, we should know). If we can implement this reliably on Android and iOS, I think it would be a fine addition to the spec but I'm not sure if we want to just return immediately.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/screen-orientation/pull/183#issuecomment-515623382

Received on Friday, 26 July 2019 22:59:59 UTC