- From: Adam Barth <w3c@adambarth.com>
- Date: Tue, 31 Jul 2012 15:26:35 -0700
- To: Vincent Scheib <scheib@google.com>
- Cc: Webapps WG <public-webapps@w3.org>, Jer Noble <jer.noble@apple.com>, whatwg <whatwg@lists.whatwg.org>, "Robert O'Callahan" <robert@ocallahan.org>, annevk@annevk.nl
It looks like the ability to go full screen is off-by-default and then enabled via the attribute. If we used iframe@sandbox, the ability would be on-by-default for non-sandboxed iframes. Adam On Tue, Jul 31, 2012 at 3:11 PM, Vincent Scheib <scheib@google.com> wrote: > [correcting Anne van Kesteren's email] > > > On Tue, Jul 31, 2012 at 3:03 PM, Vincent Scheib <scheib@google.com> wrote: > >> I'm currently implementing Pointer Lock [1] in WebKit, which was adjusted >> recently to mimic Fullscreen [2]. >> >> Why does the Fullscreen specification use an iframe attribute >> allowfullscreen to permit/restrict iframe capabilities instead of using >> iframe sandbox="allow-fullscreen"? >> >> [1] http://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html >> [2] http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html >> >>
Received on Tuesday, 31 July 2012 22:27:36 UTC