- From: Philip Jägenstedt <notifications@github.com>
- Date: Tue, 20 Oct 2015 02:07:28 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
Received on Tuesday, 20 October 2015 09:08:03 UTC
Yeah, it does look like the removing steps can end up simply calling <b>unfullscreen *node*</b> for iframes whose content document has a fullscreen element. That looks like an unrelated bug, though, probably those steps worked when fullscreen element stack had to be in tree order? --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/issues/30#issuecomment-149486232
Received on Tuesday, 20 October 2015 09:08:03 UTC