- From: <bugzilla@jessica.w3.org>
- Date: Sat, 20 Sep 2014 17:19:15 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26813 --- Comment #2 from Anne <annevk@annevk.nl> --- > you remove an ancestor of an element that's fullscreen? https://github.com/whatwg/fullscreen/commit/b9f36a4db4f298004463062f19f903a3117629bb > you remove the iframe browsing context container of the browsing context of an element that's fullscreen? That's also covered by the above. An iframe would itself be on a stack. > you navigate an ancestor browsing context of the browsing context of an element's that fullscreen? This one is up to HTML to define I think. > 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? I hate document.open() and have no good suggestions at the moment. I suspect we'd want this to exit fullscreen. > window.close() is called? Seems the same as if you hit (x) in the browser, probably exits fullscreen? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Saturday, 20 September 2014 17:19:16 UTC