- From: Philip Jägenstedt <notifications@github.com>
- Date: Thu, 01 Jun 2017 02:27:59 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 1 June 2017 09:28:34 UTC
@mounirlamouri, https://github.com/whatwg/fullscreen/pull/92 fixes my original problem in this issue but not the Screen Orientation API issues. The earliest possible time that one could fire the events I think is in a microtask following the resize, but I don't think that'd really solve anything. The orientation change itself can involve an animation and is in any event out-of-process in some implementations, so it couldn't be guaranteed to happen before the layout at which the original scale and scroll position should be restored. Maybe a good start would be to write (manual) testharness.js tests for the expected behavior that are as unforgiving timing-wise as possible. Is that something you have the bandwidth for? -- 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/74#issuecomment-305440320
Received on Thursday, 1 June 2017 09:28:34 UTC