[CORS] Applying preflight cache to an entire domain?

2012-04-18 Thread Monsur Hossain
Hi there. The CORS spec currently indicates that the preflight cache should store preflight responses for a particular origin/request url pair. That means that multiple requests to different urls on the same domain will always trigger a preflight, even if the preflight response is exactly the same

Request for FormData.remove() method

2012-04-18 Thread David Sickmiller
Hi, I must admit I am ignorant of the W3C process for drafting the XMLHttpRequest, but I see that the webpage says to send feedback to this address, so I am writing this email to submit my feedback. The new FormData(form) constructor is an especially handy way to slurp in all the data for a

Re: Request for FormData.remove() method

2012-04-18 Thread Anne van Kesteren
On Wed, 18 Apr 2012 06:50:45 +0200, David Sickmiller davesickmil...@gmail.com wrote: (I'm removing cue text from text input fields.) Could you elaborate on what cue text is? It kind of sounds like you want to use input placeholder=Name here... name=name but I'm not entirely sure. --

Re: [CORS] Applying preflight cache to an entire domain?

2012-04-18 Thread Anne van Kesteren
On Tue, 17 Apr 2012 23:35:16 +0200, Monsur Hossain mon...@gmail.com wrote: Hi there. The CORS spec currently indicates that the preflight cache should store preflight responses for a particular origin/request url pair. That means that multiple requests to different urls on the same domain

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread Henri Sivonen
On Tue, Apr 3, 2012 at 1:21 AM, Dimitri Glazkov dglaz...@chromium.org wrote: Perhaps lost among other updates was the fact that I've gotten the first draft of HTML Templates spec out: http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html Once parsed, the template contents

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread Anne van Kesteren
On Wed, 18 Apr 2012 16:49:55 +0200, Henri Sivonen hsivo...@iki.fi wrote: When implementing this, making embedded content inert is probably the most time-consuming part and just using a document fragment as a wrapper isn't good enough anyway, since for example img elements load their src even

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread Dimitri Glazkov
On Wed, Apr 18, 2012 at 7:49 AM, Henri Sivonen hsivo...@iki.fi wrote: On Tue, Apr 3, 2012 at 1:21 AM, Dimitri Glazkov dglaz...@chromium.org wrote: Perhaps lost among other updates was the fact that I've gotten the first draft of HTML Templates spec out:

Re: [CORS] Applying preflight cache to an entire domain?

2012-04-18 Thread Monsur Hossain
Ah thank you! I agree that url canonicalization is a difficult issue to solve. FWIW, I was envisioning something much simpler. The CORS spec makes it clear that cache lookup should be done by origin and request url. So instead of specifying a url to this Access-Control-Policy-Path header, it would

Re: [CORS] Applying preflight cache to an entire domain?

2012-04-18 Thread Anne van Kesteren
On Wed, 18 Apr 2012 18:34:42 +0200, Monsur Hossain mon...@gmail.com wrote: Ah thank you! I agree that url canonicalization is a difficult issue to solve. FWIW, I was envisioning something much simpler. The CORS spec makes it clear that cache lookup should be done by origin and request url.

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread Tab Atkins Jr.
On Wed, Apr 18, 2012 at 8:46 AM, Anne van Kesteren ann...@opera.com wrote: On Wed, 18 Apr 2012 16:49:55 +0200, Henri Sivonen hsivo...@iki.fi wrote: When implementing this, making embedded content inert is probably the most time-consuming part and just using a document fragment as a wrapper

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread Tab Atkins Jr.
On Wed, Apr 18, 2012 at 7:49 AM, Henri Sivonen hsivo...@iki.fi wrote: On Tue, Apr 3, 2012 at 1:21 AM, Dimitri Glazkov dglaz...@chromium.org wrote: Perhaps lost among other updates was the fact that I've gotten the first draft of HTML Templates spec out:

Re: Request for FormData.remove() method

2012-04-18 Thread Bronislav Klučka
On 18.4.2012 6:50, David Sickmiller wrote: Hi, I must admit I am ignorant of the W3C process for drafting the XMLHttpRequest, but I see that the webpage says to send feedback to this address, so I am writing this email to submit my feedback. The new FormData(form) constructor is an

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread Rafael Weinstein
On Wed, Apr 18, 2012 at 9:32 AM, Dimitri Glazkov dglaz...@chromium.org wrote: On Wed, Apr 18, 2012 at 7:49 AM, Henri Sivonen hsivo...@iki.fi wrote: On Tue, Apr 3, 2012 at 1:21 AM, Dimitri Glazkov dglaz...@chromium.org wrote: Perhaps lost among other updates was the fact that I've gotten the

Re: [webcomponents] HTML Parsing and the template element

2012-04-18 Thread James Graham
On Wed, 18 Apr 2012, Dimitri Glazkov wrote: Wouldn't it make more sense to host the template contents as normal descendants of the template element and to make templating APIs accept either template elements or document fragments as template input?  Or to make the template elements have a