- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Jul 2015 13:04:09 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26676 --- Comment #4 from Philip Jägenstedt <philipj@opera.com> --- I think the problem still remains, here: "Let descendantDocs be an ordered set consisting of doc's descendant browsing contexts' documents whose fullscreen element is non-null, if any, in reverse tree order." The definition of "descendant browsing contexts" is defined in terms of HTML's "parent browsing context": https://html.spec.whatwg.org/multipage/browsers.html#parent-browsing-context AFAICT, that's defined in terms of an <iframe> actually being in a document, so it ought to be the case still that just removing an iframe with fullscreen elements inside will leave those elements believing that they are in fullscreen, and if it's later re-inserted somewhere the results will be strange. Perhaps this can be solved inside "Whenever the removing steps run with an oldNode, run these steps." If that exits fullscreen on any element that's removed while it's in the top layer stack, even if not at the top, it ought to be fine. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 15 July 2015 13:04:14 UTC