On Tue, Oct 18, 2011 at 9:23 PM, Anne van Kesteren 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 controls you go
> UI-based fullscreen for a di
On Tue, 18 Oct 2011 23:24:27 +0900, Glenn Maynard 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 whole
browser wind
On Mon, 17 Oct 2011, Darin Fisher wrote:
> On Mon, Oct 17, 2011 at 4:31 PM, Anne van Kesteren
> wrote:
> > On Tue, 18 Oct 2011 08:11:41 +0900, Darin Fisher
> > wrote:
> >
> >> OK, I can't help myself. One more question:
> >>
> >> What should happen if the fullscreen browsing context is navigat
On Tue, Oct 18, 2011 at 7:24 AM, Glenn Maynard wrote:
> On Tue, Oct 18, 2011 at 3:55 AM, Anne van Kesteren
> 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 or
> maybe
> > a container. So you
On Tue, Oct 18, 2011 at 3:55 AM, Anne van Kesteren 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 or maybe
> a container. So your video player website is displayed fullscreen,
> because your users
On Tue, 18 Oct 2011 10:33:42 +0900, Anne van Kesteren
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
top-level browsing
On Tue, 18 Oct 2011 10:00:51 +0900, Chris Pearce
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 cross-domain
and
On 18/10/2011 12:52 p.m., Darin Fisher wrote:
On Mon, Oct 17, 2011 at 4:17 PM, Anne van Kesteren wrote:
On Tue, 18 Oct 2011 07:55:33 +0900, Darin Fisher
wrote:
Thanks for working on this spec! I have more questions, but I'll just
start with one. If enterFullscreen() is called when the brow
On Mon, Oct 17, 2011 at 4:17 PM, Anne van Kesteren wrote:
> On Tue, 18 Oct 2011 07:55:33 +0900, Darin Fisher
> 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 displ
On Mon, Oct 17, 2011 at 4:31 PM, Anne van Kesteren wrote:
> On Tue, 18 Oct 2011 08:11:41 +0900, Darin Fisher
> 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 fulls
On Tue, 18 Oct 2011 08:11:41 +0900, Darin Fisher
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 out of fullscreen m
On Tue, 18 Oct 2011 07:55:33 +0900, Darin Fisher
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 like
Safari 5.1 igno
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 Fisher
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 al
14 matches
Mail list logo