Re: [fullscreen] Allow fullscreen to be triggered by an orientation change event (#34)

It sounds like a bad frame is confirmed by your testing, and that problem will neither grow nor shrink by waiting. If the orientation change event is eventually spec'd and implemented similarly to fullscreen, i.e. it is fired as an animation frame task at the first frame after the transition, then no amount of later polish could close this gap. In other words, to fix the problem later would by necessity duplicate the "fullscreen on rotate" functionality in some way.

So, what would it take to guarantee no bad frames, at a minimum? An alternative to teaching the orientation API about fullscreen could be to teach the fullscreen API about orientation:
```JavaScript
element.requestFullscreen({ requireOrientation: 'landscape' });
```
If we're already in landscape *and* there's a user gesture it could go fullscreen immediately, and otherwise it'll wait for a rotation. Might benefit from cancelable promises to cancel the request before it happens, but a v1 without that might be OK too.

Maybe. Other ideas?

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/34#issuecomment-197930818