- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Feb 2015 11:34:34 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26813 --- Comment #12 from Philip Jägenstedt <philipj@opera.com> --- Consider me back at work, at least as far as reading and replying to fullscreen bug mail is concerned. These three seem to be unresolved: > * you navigate an ancestor browsing context of the browsing context of an > element's that fullscreen? That ancestor must then have an iframe which is the fullscreen element, so there shouldn't be anything special about this. Is the standard case of navigating a document with a fullscreen element handled well, spec-wise? > * the document that the fullscreen element is in has its document.open() > method invoked, causing the Document to be recycled but the element to go > away? Does this not indirectly invoke the "Whenever the removing steps run with an oldNode, run these steps" bit in the Fullscreen spec? > * window.close() is called? Uh... "fully exit fullscreen" seems appropriate. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 16 February 2015 11:34:38 UTC