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
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,
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
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
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
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
Hi Anne,
Thanks for working on this spec! I have more questions, but I'll just start
with one. If enterFullscreen() is called when the browsing context is
already being displayed fullscreen, what should happen? (It looks like
Safari 5.1 ignores the second call to webkitRequestFullScreen.)
I
OK, I can't help myself. One more question:
What should happen if the fullscreen browsing context is navigated? What
happens if the document, containing the fullscreen element, is destroyed?
Perhaps it should bounce out of fullscreen mode?
-Darin
On Mon, Oct 17, 2011 at 3:55 PM, Darin
On Tue, 18 Oct 2011 07:55:33 +0900, Darin Fisher da...@chromium.org
wrote:
Thanks for working on this spec! I have more questions, but I'll just
start with one. If enterFullscreen() is called when the browsing
context is
already being displayed fullscreen, what should happen? (It looks
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 context is navigated? What
happens if the document, containing the fullscreen element, is destroyed?
Perhaps it should bounce
On 18/10/2011 12:52 p.m., Darin Fisher wrote:
On Mon, Oct 17, 2011 at 4:17 PM, Anne van Kesterenann...@opera.com wrote:
On Tue, 18 Oct 2011 07:55:33 +0900, Darin Fisherda...@chromium.org
wrote:
Thanks for working on this spec! I have more questions, but I'll just
start with one. If
On Tue, 18 Oct 2011 10:00:51 +0900, Chris Pearce cpea...@mozilla.com
wrote:
Yeah, I suggest that if requestFullScreen() is called when another
element is already the fullscreen element, the new requestee should
become the fullscreen element.
A use case for this is: a fullscreen page with a
12 matches
Mail list logo
