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

2012-07-31 Thread Adam Barth
On Tue, Jul 31, 2012 at 10:24 PM, Robert O'Callahan wrote: > On Wed, Aug 1, 2012 at 10:33 AM, Adam Barth 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, s

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

2012-07-31 Thread Robert O'Callahan
On Wed, Aug 1, 2012 at 10:33 AM, Adam Barth 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 > -> >

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

2012-07-31 Thread Adam Barth
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 -> -> Can c.html go full screen? Where is that specified? Adam

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

2012-07-31 Thread Adam Barth
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 wrote: > [correcting Anne van Kesteren's email] > > >

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

2012-07-31 Thread Vincent Scheib
[correcting Anne van Kesteren's email] On Tue, Jul 31, 2012 at 3:03 PM, Vincent Scheib 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 pe

allowfullscreen vs sandbox="allow-fullscreen", and mimicking for pointer lock

2012-07-31 Thread Vincent Scheib
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.o

Re: [selectors-api] RfC: LCWD of Selectors API Level 1; deadline July 19

2012-07-31 Thread Arthur Barstow
On 7/19/12 11:15 PM, ext Kang-Hao (Kenny) Lu wrote: Sorry for my late comment. While I think it's fine to publish LCWD Selectors API as it is, it would be nice if it can address my comment in [1]. By "address", I mean either define the desired behavior or explicitly mark it as undefined (which I

Re: [gamepad] Polling access point

2012-07-31 Thread Ted Mielczarek
On Thu, Jul 26, 2012 at 9:20 PM, Scott Graham wrote: > There's no particular indication at the spec level to indicate stopping the > gamepad polling, based on the assumption that it's an implementation detail. > Maybe there should be some way for content to hint that though? > > I guess an impleme

F2F meeting Oct 29-30 in Lyon France; registration deadline Oct 16

2012-07-31 Thread Arthur Barstow
Hi All, As announced earlier, WebApps will have a f2f meeting October 29-30 as part of the W3C's annual Technical Plenary Week in Lyon France. WebApps' meeting page is . We will again preallocate some time slo

Re: CORS spec error (?)

2012-07-31 Thread Anne van Kesteren
On Mon, Jul 30, 2012 at 1:49 PM, wrote: > I think that there's a problem with the current spec of CORS. > When attempting to perform a preflight with a non-anonymous website, the > preflight is bound to fail because no Authorization header is being sent. > This poses a problem at least for IIS us

[no subject]

2012-07-31 Thread ewolfman
Hi,I think that there's a problem with the current spec of CORS.When attempting to perform a preflight with a non-anonymous website, the preflight is bound to fail because no Authorization header is being sent.This poses a problem at least for IIS users who are using a Classic Application Pool, and

[no subject]

2012-07-31 Thread ewolfman
Hi,I think that there's a problem with the current spec of CORS.When attempting to perform a preflight with a non-anonymous website, the preflight is bound to fail because no Authorization header is being sent.This poses a problem at least for IIS users who are using a Classic Application Pool, and