- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Thu, 24 Jan 2013 11:44:36 -0500
- To: Anne van Kesteren <annevk@annevk.nl>
- CC: public-webapps@w3.org
On 1/24/13 9:22 AM, Anne van Kesteren wrote: > On Thu, Jan 24, 2013 at 3:19 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> That seems overly broad. For example, navigating to a named anchor should >> not exit fullscreen, in my opinion. Is there no sufficiently-late step in >> the navigate algorithm that this can hook into? > > The navigate algorithm defines this, I have not studied the > particulars, but I believe scrolling to a named anchor should work > fine. Just thinking that maybe we should allow same-origin navigation > too. How would that work, exactly? Fullscreen is requested on a particular element, last I checked. Once you get to the point where that element's owner document is not the document being displayed, how is that element supposed to say fullscreen in a reasonable way? -Boris
Received on Thursday, 24 January 2013 16:45:07 UTC