Looking at the behavior of existing implementations, we don't seem to
have committed to how to handle redirects in CORS yet:
IE8 (XDomainRequest): Redirects are not supported
Firefox 3.5: If you start off same-origin, you can redirect
cross-origin once, and the Origin header gets added at that
2009/9/21 Arthur Barstow art.bars...@nokia.com:
Hi Marcos,
On Sep 21, 2009, at 2:08 PM, ext Marcos Caceres wrote:
For the sake of the DoC, can you please acknowledge that the comments
below have been addressed and your are satisfied with the way the WG
addressed your comments.
Based on
Hi,
while writing tests, we've hit upon something that could use a little
clarification: the distinction between skip and ignore.
One interpretation that we can come to is that the two terms means the
same thing for files and attributes, but for XML element processing
ignore descends
Hi,
I'm planning to look at beginning work on Selectors API v2 soon to
add a number of requested features that didn't make it into the first
version. This e-mail is a summary of what is being considered, and is
intended to start discussion about which ones are really worth focussing
on,
Below is the draft agenda for the September 24 Widgets Voice
Conference (VC).
Inputs and discussion before the VC on all of the agenda topics via
public-webapps is encouraged).
Please address Open/Raised Issues and Open Actions before the meeting:
On Tue, 22 Sep 2009 20:38:46 +0200, Collin Jackson
col...@collinjackson.com wrote:
Proposal
Same-origin redirects are allowed. Redirects from same-origin to
cross-origin are also allowed. When processing a redirect from one
foreign origin to another, the browser replaces the Origin header with
My first priority would be Matches Selector, and see to that
it fulfills the needs for event delegation.
Best regards
Mike Wilson
Lachlan Hunt wrote:
Hi,
I'm planning to look at beginning work on Selectors API v2 soon to
add a number of requested features that didn't make it into the
Hi,
The attribute uri on the access element in WARP is somewhat
misleading - what it takes is more a URL pattern than a URI. I would
suggest renaming it in urlpattern or just pattern (unless there are
already many implementations that rely on that attribute name).
There may be lessons to be
Hi Art, All,
I would like to suggest to add to the agenda the point that appeared during the
widgets testing event.
It is related to the Widget Interface, View Modes and patterns.
The comments below will be valid also as LC comments to the Widget Interface.
The Widget Interface includes width
On Sep 19, 2009, at 15:00 , Charles McCathieNevile wrote:
On Sat, 19 Sep 2009 07:55:23 +0200, Garrett Smith dhtmlkitc...@gmail.com
wrote:
In looking at the credits, I noticed all of:
Bjoern Hoehrmann, Björn Hoehrmann, Björn Höhrmann, Bjoern H�hrmann
I am not sure if there are two similar
Hi,
One more comment to the below:
There is one use case not handled by the below scenarios:
In case the width/height are dropped on the Widget interface, the widget would
not know the initial dimensions.
E.g. in Win32 each new window get WM_SIZE event with the initial width/height.
However, I
On Sep 21, 2009, at 20:08 , Marcos Caceres wrote:
5.1
Localization
Shall it be possible for the widget to programmatically discover
the localization path it was loaded from (section 9 of PC)?
Yes, you can check its URI. If the implementation supports the window
object, then it possible.
Robin Berjon wrote:
On Sep 21, 2009, at 20:08 , Marcos Caceres wrote:
5.1
Localization
Shall it be possible for the widget to programmatically discover the
localization path it was loaded from (section 9 of PC)?
Yes, you can check its URI. If the implementation supports the window
object,
On Tue, 25 Aug 2009 17:34:18 +0200, Julian Reschke julian.resc...@gmx.de
wrote:
was it ever discussed to expose information from provisional HTTP
responses
(http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.10.1) to
clients?
That might become interesting once extensions such as
On Wed, 23 Sep 2009 15:33:22 +0200, Robin Berjon ro...@berjon.com wrote:
On Sep 19, 2009, at 15:00 , Charles McCathieNevile wrote:
On Sat, 19 Sep 2009 07:55:23 +0200, Garrett Smith
dhtmlkitc...@gmail.com wrote:
In looking at the credits, I noticed all of:
Bjoern Hoehrmann, Björn Hoehrmann,
On Wed, Sep 23, 2009 at 12:44 PM, Robin Berjon ro...@berjon.com wrote:
Hi,
while writing tests, we've hit upon something that could use a little
clarification: the distinction between skip and ignore.
One interpretation that we can come to is that the two terms means the same
thing for
On Wed, 12 Aug 2009 18:03:52 +0200, Stewart Brodie
stewart.bro...@antplc.com wrote:
The Abstract is good for an abstract, but I don't think it's got enough
detail in it for a list of differences. I'll review the new documents in
closer detail when I get a chance and see if I can suggest some
On Wed, 23 Sep 2009 02:18:02 +0200, Arthur Barstow art.bars...@nokia.com
wrote:
Given WebApps' CORS spec, this Workshop (November 17-18 in Luxembourg)
may be of interest to you:
http://www.w3.org/2009/policy-ws/cfp.html
Thanks Art. I looked into this and couldn't really figure out how
On Wed, Sep 23, 2009 at 5:34 AM, Anne van Kesteren ann...@opera.com wrote:
For simple cross-origin requests Origin would be a space-separated list of
origins indicating the redirect chain.
When we used this syntax for the Sec-From header, Mark Nottingham
advocated using commas to separate the
2009/9/17 Robin Berjon ro...@berjon.com:
On Sep 3, 2009, at 14:25 , Marcos Caceres wrote:
Many specifications in the Web stack depend on a context being defined
that includes a current IRI. This is easily provided for documents
retrieved over HTTP, or from the local file system, but is
All,
I think we all appreciate frank and open technical discussions about
the Web Applications WG's specifications but we must also be
respectful and professional in our exchanges.
My personal tolerance for terse exchanges is relatively high but that
is not true for everyone and we must
2009/9/15 Marcin Hanclik marcin.hanc...@access-company.com:
The below comments refer to:
Widgets 1.0: The widget Interface
Editor's Draft 14 September 2009
General:
Replace can with may in the whole document.
I've used can deliberately throughout the document where statements of
fact are
On Wed, Sep 23, 2009 at 4:36 PM, Marcin Hanclik
marcin.hanc...@access-company.com wrote:
Hi,
One more comment to the below:
There is one use case not handled by the below scenarios:
In case the width/height are dropped on the Widget interface, the widget
would not know the initial
Hi Art, Anne,
looks like the focus of the CORS specification is on very simple
access control that would just express that site A allows access to
content if the javascript stuff calls it from a thing found on site
B.
The workshop deals with conditions (policy) under which a certain
Hmm, I raised this one too.
I can't see how the origin handles instances exactly, and the concept
of origin doesn't seem all that relevant to our implementation
anyway - it looks more like something for browser makers to worry over?
Why is origin of a widget preferable to instance of
Below are comments regarding rev1.1 of the View Modes Media Feature
spec:
http://dev.w3.org/cvsweb/2006/waf/widgets-vm/vm-mediafeature.src.html
-Regards, Art Barstow
1. Abstract:
a. I don't understand the document's content in this context.
b. Missing a sentence terminator for the first
Mike Wilson wrote:
My first priority would be Matches Selector, and see to that
it fulfills the needs for event delegation.
Is there any special functionality that would be needed to achieve this?
If I understand correctly, event delegation just needs to be able to
check whether the event
This sounds like a good idea. One thing we can do to reduce the
complexity is to have different grammars for server conformance and
for user agent conformance. Essentially, servers would be required to
conform to the current grammar, but UAs would be required to conform
to the more tolerant
On Wed, Sep 23, 2009 at 4:51 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
*Scoped Queries*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5860
This has been discussed extensively in the past. Basically, the idea is
that the selector would be evaluated in the scope of the element, in a way
Jonas Sicking wrote:
On Wed, Sep 23, 2009 at 4:51 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
*Scoped Queries*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5860
This has been discussed extensively in the past. Basically, the idea is
that the selector would be evaluated in the scope
I think a couple of those features are pretty low priority:
- I don't see the point of collective queries on NodeLists.
Are there any references for the proposal?
Otherwise I can't think of any useful queries that can't already be
achieved with a single querySelectorAll().
- Filtering
On Wed, Sep 23, 2009 at 4:51 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
Hi,
I'm planning to look at beginning work on Selectors API v2 soon to add a
number of requested features that didn't make it into the first version.
This e-mail is a summary of what is being considered, and is
Quick Summary of my opinions:
Matches Selector: Super-super useful - critical, in fact. We're not able to
remove jQuery's selector engine until this is implemented. I'm working with
the devs at Mozilla to get an implementation landed. Already have a test
suite in place.
Filtering
On Wed, Sep 23, 2009 at 8:17 PM, John Resig jere...@gmail.com wrote:
Quick Summary of my opinions:
Matches Selector: Super-super useful - critical, in fact. We're not able to
remove jQuery's selector engine until this is implemented. I'm working with
the devs at Mozilla to get an
John Resig wrote:
Libraries already parse selector queries anyway. And some of them
add non-standard selectors and presumeably will continue to do so.
I don't think it is an issue.
However the parsing only happens after the selector has been passed to
the native querySelectorAll
Jonas Sicking wrote:
On Wed, Sep 23, 2009 at 6:00 PM, Sean Hogan shogu...@westnet.com.au wrote:
Jonas Sicking wrote:
On Wed, Sep 23, 2009 at 4:51 AM, Lachlan Hunt lachlan.h...@lachy.id.au
wrote:
*Scoped Queries*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5860
This has been
On Sep 23, 2009, at 5:26 PM, Jonas Sicking wrote:
On Wed, Sep 23, 2009 at 4:51 AM, Lachlan Hunt lachlan.h...@lachy.id.au
wrote:
*Scoped Queries*
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5860
This has been discussed extensively in the past. Basically, the
idea is
that the selector
37 matches
Mail list logo
