W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] Fullscreen feedback

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 23 Aug 2010 18:33:06 +1200
Message-ID: <AANLkTimaDR7yB1xCad8CnJBWdw7OdENL6e6cmiCx=PQy@mail.gmail.com>
On Mon, Aug 23, 2010 at 5:25 PM, Adam Barth <w3c at adambarth.com> wrote:

> So...  The trade-off is:
> 1) Only browsing contexts can go full-screen (since they have URLs
> that we could display).
> 2) Any element can go full-screen, but we'll need to add a nasty
> non-semantic attribute.

Is "allowfullscreen" really less semantic than "sandbox"?

Actually one option here is to only allow sandboxed iframes to go
fullscreen, deny fullscreen to sandboxed iframes by default, and provide a
sandbox token (e.g. "allow-fullscreen") that allows fullscreen. So you could
add sandbox="allow-scripts allow-fullscreen" to a video embedding IFRAME.

Another idea is that we could let any element go full-screen, but then
> we'd show the URL of its browsing context.  There's some subtleties
> here about overlays from parent frames, but those seem solvable.

Doable, but maybe painful to implement, and there are numerous spec and UI
issues to do with navigation, history, etc.

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100823/2ae8a3b9/attachment-0001.htm>
Received on Sunday, 22 August 2010 23:33:06 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:26 UTC