W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2012

Re: [whatwg] allowfullscreen vs sandbox="allow-fullscreen", and mimicking for pointer lock

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 31 Jul 2012 15:26:35 -0700
Message-ID: <CAJE5ia9T7NvPBSLd_P2Ak-uA7S57DEqtb6xQ-t0BUxLPV3O6Ew@mail.gmail.com>
To: Vincent Scheib <scheib@google.com>
Cc: whatwg <whatwg@lists.whatwg.org>, Webapps WG <public-webapps@w3.org>, Robert O'Callahan <robert@ocallahan.org>, Jer Noble <jer.noble@apple.com>
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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:09 GMT