The registration page for the April 24 Web Components f2f meeting at
Google's Mount View CA office is now open:
https://www.w3.org/2002/09/wbs/42538/webcomponents-042015/
The meeting/agenda page is:
https://www.w3.org/wiki/Webapps/WebComponentsApril2015Meeting.
Please register by April 10.
On Mon, Feb 23, 2015 at 8:42 PM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Feb 23, 2015 at 11:06 AM, Anne van Kesteren ann...@annevk.nl wrote:
That combined with requiring to list
the explicit origin has worked well for CORS so far.
This could potentially help.
I don't remember the
On Tue, Feb 24, 2015 at 4:35 PM, Dimitri Glazkov dglaz...@google.com wrote:
Wait, what do you mean by that is what custom elements provide for today..
The entire pattern of template-stamping depends on the fact that custom
elements aren't broken when cloning/importing.
There's no hook for
On Tue, Feb 24, 2015 at 12:14 AM, Anne van Kesteren ann...@annevk.nl
wrote:
On Mon, Feb 23, 2015 at 11:58 PM, Ryosuke Niwa rn...@apple.com wrote:
In that regard, perhaps what we need another option (although 4 might be
a developer friendly superset of this):
5) Don't do anything. Custom
Filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=28092 to add more data
to the informative content around the normative statement that makes this
happen.
On Tue, Feb 24, 2015 at 7:39 AM, Dimitri Glazkov dglaz...@google.com
wrote:
On Tue, Feb 24, 2015 at 7:37 AM, Anne van Kesteren
On Tue, Feb 24, 2015 at 7:37 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Tue, Feb 24, 2015 at 4:35 PM, Dimitri Glazkov dglaz...@google.com
wrote:
Wait, what do you mean by that is what custom elements provide for
today..
The entire pattern of template-stamping depends on the fact
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28092
Bug ID: 28092
Summary: [Custom]: Clarify in informative note that
cloning/importing also enqueues created callback
Product: WebAppsWG
Version: unspecified
Hardware: PC
On Tue, Feb 24, 2015 at 3:25 AM, Anne van Kesteren ann...@annevk.nl wrote:
If that's the case then I think we'd get most of the functionality,
with essentially none of the risk, by only allowing server-wide
cookie-less preflights.
If we only do it for this, could we combine that feature with
