W3C home > Mailing lists > Public > public-webmediaapi@w3.org > May 2017

Re: How should devices that are always in fullscreen mode implement the Fullscreen API?

From: Vickers, Mark <Mark_Vickers@comcast.com>
Date: Wed, 31 May 2017 10:04:09 +0000
To: Anne van Kesteren <annevk@annevk.nl>
CC: "public-webmediaapi@w3.org" <public-webmediaapi@w3.org>
Message-ID: <B27E85AF-CDAA-423F-9337-A9E40C2281D1@comcast.com>
Hi again Anne,

We had quite a bit of discussion in our group about how the fullscreen API works in devices like smart TVs that may run a chrome-less browser that is always full screen size.
	https://github.com/w3c/webmediaapi/issues/22

We did finally reach consensus that the fullscreen API should operate fine in this use case as currently specified.

I was asked to send a note that it might be useful for the fullscreen spec to informatively mention that an implementation without any browser chrome can just have the top level document's "normal" dimensions be the same as "the dimensions of the screen of the output device".

Thanks,
mav

> On Feb 23, 2017, at 12:32 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> 
> On Wed, Feb 22, 2017 at 4:46 PM, Vickers, Mark <Mark_Vickers@comcast.com> wrote:
>> Haven't chatted in a while. Hope all is well with you.
> 
> All is well, fortunately. And likewise!
> 
> 
>> 1. Does the Fullscreen API have a model for how devices that are always in fullscreen mode should implement the Fullscreen API?
> 
> We don't really at the moment, though they could. An aspect of the
> Fullscreen API is that it fullscreens a particular element, which has
> some advantages for developers even when the application always takes
> up most of the screen.
> 
> 
>> 2. Should TVs and TV-connected devices simply follow the iOS and Android model and not implement this API?
> 
> I don't really know the motivation behind those platforms not exposing
> the API so I'm probably not the right person to ask.
> 
> 
> -- 
> https://annevankesteren.nl/
> 
Received on Wednesday, 31 May 2017 10:04:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 31 May 2017 10:04:47 UTC