Re: [whatwg] Entering fullscreen when already in fullscreen mode [was: Fullscreen]

2011-10-18 Thread Anne van Kesteren
On Tue, 18 Oct 2011 10:33:42 +0900, Anne van Kesteren ann...@opera.com wrote: Site A embeds site B. Site A goes fullscreen. Site B does requestFullscreen(). Site B does exitFullscreen(). Site A is no longer fullscreen. Either we need to base fullscreen on browsing contexts rather than

Re: [whatwg] Entering fullscreen when already in fullscreen mode [was: Fullscreen]

2011-10-18 Thread Glenn Maynard
On Tue, Oct 18, 2011 at 3:55 AM, Anne van Kesteren ann...@opera.com wrote: However, I just realized this does not work for the single document case. You have a video player website and you host your videos in video or maybe a div container. So your video player website is displayed fullscreen,

Re: [whatwg] Another bug in the HTML parsing spec?

2011-10-18 Thread David Flanagan
On 10/17/11 5:47 PM, Ian Hickson wrote: On Mon, 17 Oct 2011, David Flanagan wrote: In the HTML spec, The rules for parsing tokens in foreign content include an algorithm for any other end tag. This is the algorithm at the very end of

Re: [whatwg] How should overflow be handled when parsing integers?

2011-10-18 Thread Daniel Bates
On Oct 16, 2011, at 11:02 AM, Mounir Lamouri wrote: On 10/16/2011 02:17 PM, Daniel Bates wrote: How should overflow be handled when parsing integers? Step 8 of the parsing algorithm in bothhttp://dev.w3.org/html5/spec/Overview.html#rules-for-parsing-integers

Re: [whatwg] Entering fullscreen when already in fullscreen mode [was: Fullscreen]

2011-10-18 Thread Darin Fisher
On Tue, Oct 18, 2011 at 7:24 AM, Glenn Maynard gl...@zewt.org wrote: On Tue, Oct 18, 2011 at 3:55 AM, Anne van Kesteren ann...@opera.com wrote: However, I just realized this does not work for the single document case. You have a video player website and you host your videos in video or

Re: [whatwg] Fullscreen

2011-10-18 Thread Ian Hickson
On Mon, 17 Oct 2011, Chris Pearce wrote: On 15/10/2011 5:27 p.m., Anne van Kesteren wrote: http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html Defining when exactly the fullscreen enabled flag is set for Document objects I will leave up to HTML. As well as defining the

Re: [whatwg] Entering fullscreen when already in fullscreen mode [was: Fullscreen]

2011-10-18 Thread Ian Hickson
On Mon, 17 Oct 2011, Darin Fisher wrote: On Mon, Oct 17, 2011 at 4:31 PM, Anne van Kesteren ann...@opera.com wrote: On Tue, 18 Oct 2011 08:11:41 +0900, Darin Fisher da...@chromium.org wrote: OK, I can't help myself. One more question: What should happen if the fullscreen browsing

Re: [whatwg] Entering fullscreen when already in fullscreen mode [was: Fullscreen]

2011-10-18 Thread Anne van Kesteren
On Tue, 18 Oct 2011 23:24:27 +0900, Glenn Maynard gl...@zewt.org wrote: Do you mean the user-fullscreen mode that most browsers enter with F11? Not necessarily. You run into the same issue with requestFullscreen() usage. That's a separate piece of state entirely, since it affects the

Re: [whatwg] Entering fullscreen when already in fullscreen mode [was: Fullscreen]

2011-10-18 Thread Glenn Maynard
On Tue, Oct 18, 2011 at 9:23 PM, Anne van Kesteren ann...@opera.com wrote: I think it would be kind of nice if the UI and API-based fullscreen were aligned. Otherwise you run into all kinds of odd situations. E.g. API-based fullscreen first. Then via native video controls you go UI-based

[whatwg] Fullscreen Update

2011-10-18 Thread Anne van Kesteren
1) How much should UI-based and API-based fullscreen interact? To me it seems nice if pressing F11 would also give you fullscreenchange events and that Document.fullscreen would yield true. Why would you not want to give the same presentation via native activation and API-based activation?