On Jan 9, 2010, at 1:57 PM, Tyler Close wrote:
On Sat, Jan 9, 2010 at 10:20 AM, Adam Barth w...@adambarth.com wrote:
(As Maciej says, CORS doesn't appear to have this hole.)
Indeed, I misread the section on simple requests:
http://www.w3.org/TR/access-control/#simple-cross-origin-request0
On 8/01/10 1:19 AM, Lachlan Hunt wrote:
Hi,
Now that Selectors API Level 1 is published and basically all but
finalised (just waiting for some implementations to be officially
released before taking it to REC), can we publish Selectors API Level
2 as an FPWD?
It would be useful to have it
Sean Hogan wrote:
On 8/01/10 1:19 AM, Lachlan Hunt wrote:
can we publish Selectors API Level 2 as an FPWD?
http://dev.w3.org/2006/webapi/selectors-api2/
FYI, it seems the whole Status of this Document hasn't been updated for
Selectors-API2.
Yeah, that will get fixed up when I get the spec
On Sat, Jan 9, 2010 at 10:50 AM, Adam Barth w...@adambarth.com wrote:
The UMP spec says:
[[
The user agent must not add any information obtained from: HTTP
cookies, HTTP Auth headers, client certificates, or the referring
resource, including its origin (other than the request parameters).
I don't quite understand this part of that text:
[[
In this case, the request
sent by the user-agent is not a uniform request; however, the request
ultimately delivered to the resource host will be, since any
Proxy-Authorization request header is removed by the proxy before
forwarding the request
On Sun, Jan 10, 2010 at 6:54 AM, Maciej Stachowiak m...@apple.com wrote:
What I meant to say was that the weak confidentiality
protection for ECMAScript should not be used as an excuse to weaken
protection for other resources.
And I was never proposing to weaken existing protection for other
On 11/01/10 8:29 AM, Lachlan Hunt wrote:
Sean Hogan wrote:
On 8/01/10 1:19 AM, Lachlan Hunt wrote:
can we publish Selectors API Level 2 as an FPWD?
http://dev.w3.org/2006/webapi/selectors-api2/
I can't see the value of queryScopedSelector*() methods. The original
rationale was that JS
On 1/10/10 11:58 PM, Sean Hogan wrote:
Even if jQuery deprecates non-standard selectors, the current spec for
queryScopedSelector*() doesn't support the jQuery implicitly scoped
selector *.
As I understand it, jquery selectors on elements are always scoped in
the sense that they behave
On 11/01/10 4:19 PM, Boris Zbarsky wrote:
On 1/10/10 11:58 PM, Sean Hogan wrote:
Even if jQuery deprecates non-standard selectors, the current spec for
queryScopedSelector*() doesn't support the jQuery implicitly scoped
selector *.
As I understand it, jquery selectors on elements are always
On 11/01/10 5:24 PM, Sean Hogan wrote:
On 11/01/10 4:19 PM, Boris Zbarsky wrote:
On 1/10/10 11:58 PM, Sean Hogan wrote:
Even if jQuery deprecates non-standard selectors, the current spec for
queryScopedSelector*() doesn't support the jQuery implicitly scoped
selector *.
As I understand it,
On 1/11/10 1:24 AM, Sean Hogan wrote:
That's correct. jQuery's $(element).find(div) is the equivalent of
SelectorsAPI2's element.querySelectorAll(:scope div) or
So in fact jquery can simply implement Element.find in terms of
querySelectorAll by just prepending :scope to the selector string,
11 matches
Mail list logo
