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,
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,
On Mon, Jul 30, 2012 at 1:49 PM, ewolf...@yahoo.com 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
Hi All,
As announced earlier, WebApps will have a f2f meeting October 29-30 as
part of the W3C's annual Technical Plenary Week
http://www.w3.org/2012/10/TPAC/ in Lyon France.
WebApps' meeting page is
http://www.w3.org/wiki/Webapps/TPAC2012Meeting. We will again
preallocate some time slots
On Thu, Jul 26, 2012 at 9:20 PM, Scott Graham scot...@chromium.org 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
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
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]
[correcting Anne van Kesteren's email]
On Tue, Jul 31, 2012 at 3:03 PM, Vincent Scheib sch...@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
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 sch...@google.com wrote:
[correcting Anne van
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
On Wed, Aug 1, 2012 at 10:33 AM, Adam Barth w...@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
11 matches
Mail list logo
