W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

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

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 31 Jul 2012 23:47:58 -0700
Message-ID: <CAJE5ia9swH61bfYk-TVNCZ0g6fxKzifSYeD3RRRRKrSK_ep1Xg@mail.gmail.com>
To: robert@ocallahan.org
Cc: Vincent Scheib <scheib@google.com>, Webapps WG <public-webapps@w3.org>, Jer Noble <jer.noble@apple.com>, whatwg <whatwg@lists.whatwg.org>, annevk@annevk.nl
On Tue, Jul 31, 2012 at 10:24 PM, Robert O'Callahan
<robert@ocallahan.org> wrote:
> On Wed, Aug 1, 2012 at 10:33 AM, Adam Barth <w3c@adambarth.com> wrote:
>> It's not clear to me from the spec how the allowfullscreen attribute
>> works.  It appears to be mentioned only in the security and privacy
>> considerations section.  For example, suppose I have three frames:
>>
>> Main frame: a.html
>>   -> <iframe src="b.html">
>>     -> <iframe src="c.html" allowfullscreen>
>>
>> Can c.html go full screen?  Where is that specified?
>
> The intent is that no, it can't. You're right that this is currently
> unspecified.

Even if we don't use the iframe@sandbox syntax, it might be worth
re-using the spec machinery because it's good at solving problems like
the above.

Adam
Received on Wednesday, 1 August 2012 06:49:10 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:54 GMT