Re: [whatwg/fullscreen] Allow requestFullscreen() to be called from an orientation change event (closes #34) (#43)

I picked up the term "bad frame" from the [Intent to Deprecate: overflowchanged event](https://groups.google.com/a/chromium.org/d/msg/blink-dev/1RCzsyEyNU8/gs7gLOjIU78J) on blink-dev two years ago, I don't know if this is what it's usually called.

But let me illustrate it with commented code:

```JavaScript
screen.orientation.addEventListener('change', function() {
  // called in the first animation frame task after the user rotates
  // the viewport width and height have changed and there will be a layout before the next paint
  someElement.requestFullscreen();
  document.addEventListener('fullscreenchange', function() {
    // called in the first animation frame task after going fullscreen
    // the viewport size (most likely height) has changed again
    // there will be a layout before the next paint
    // probably some things will move vertically
  });
});

---
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/pull/43#issuecomment-233700921