Re: Custom Elements: is=

2015-06-08 Thread Alice Boxhall
Did anyone have any further thoughts on this? My concerns haven't changed. On Sat, May 9, 2015 at 3:34 PM, Alice Boxhall aboxh...@google.com wrote: On Thu, May 7, 2015 at 1:00 AM, Anne van Kesteren ann...@annevk.nl wrote: On Wed, May 6, 2015 at 6:59 PM, Alice Boxhall aboxh...@google.com

Re: Custom Elements: is=

2015-06-08 Thread Alice Boxhall
On Mon, Jun 8, 2015 at 3:12 PM, Ryosuke Niwa rn...@apple.com wrote: On Jun 8, 2015, at 2:16 PM, Alice Boxhall aboxh...@google.com wrote: Did anyone have any further thoughts on this? My concerns haven't changed. Nothing new. On Sat, May 9, 2015 at 3:34 PM, Alice Boxhall

Re: Custom Elements: is=

2015-06-08 Thread Ryosuke Niwa
On Jun 8, 2015, at 2:16 PM, Alice Boxhall aboxh...@google.com wrote: Did anyone have any further thoughts on this? My concerns haven't changed. Nothing new. On Sat, May 9, 2015 at 3:34 PM, Alice Boxhall aboxh...@google.com wrote: On Thu, May 7, 2015 at 1:00 AM, Anne van Kesteren

Re: Custom Elements: is=

2015-06-08 Thread Justin Fagnani
And I'm still concerned that removing is= would severely harm the cases where you need access to special parsing behavior like template and style. On Mon, Jun 8, 2015 at 2:16 PM, Alice Boxhall aboxh...@google.com wrote: Did anyone have any further thoughts on this? My concerns haven't changed.

Re: Custom Elements: is=

2015-06-08 Thread Ryosuke Niwa
On Jun 8, 2015, at 3:23 PM, Alice Boxhall aboxh...@google.com wrote: On Mon, Jun 8, 2015 at 3:12 PM, Ryosuke Niwa rn...@apple.com mailto:rn...@apple.com wrote: On Jun 8, 2015, at 2:16 PM, Alice Boxhall aboxh...@google.com mailto:aboxh...@google.com wrote: Web developers are already

Re: Custom Elements: is=

2015-06-08 Thread Alice Boxhall
On Mon, Jun 8, 2015 at 4:23 PM, Ryosuke Niwa rn...@apple.com wrote: On Jun 8, 2015, at 3:23 PM, Alice Boxhall aboxh...@google.com wrote: On Mon, Jun 8, 2015 at 3:12 PM, Ryosuke Niwa rn...@apple.com wrote: On Jun 8, 2015, at 2:16 PM, Alice Boxhall aboxh...@google.com wrote: Web developers

Re: Custom Elements: is=

2015-06-08 Thread Ryosuke Niwa
On Jun 8, 2015, at 4:37 PM, Alice Boxhall aboxh...@google.com wrote: On Mon, Jun 8, 2015 at 4:23 PM, Ryosuke Niwa rn...@apple.com wrote: On Jun 8, 2015, at 3:23 PM, Alice Boxhall aboxh...@google.com wrote: On Mon, Jun 8, 2015 at 3:12 PM, Ryosuke Niwa rn...@apple.com wrote: On

Re: CORS performance proposal

2015-06-08 Thread Martin Thomson
On 8 June 2015 at 21:30, Nottingham, Mark mnott...@akamai.com wrote: A header denoting site-wide metadata would work for this too, of course, if folks were comfortable with the security properties of doing that (as well as the potential response overhead). The security properties bother me

Re: CORS performance proposal

2015-06-08 Thread Nottingham, Mark
Picking up an old thread... On 20 Feb 2015, at 12:54 pm, Bjoern Hoehrmann derhoe...@gmx.net wrote: * Martin Thomson wrote: On 20 February 2015 at 11:39, Bjoern Hoehrmann derhoe...@gmx.net wrote: The proposal is to use `OPTIONS * HTTP/1.1` not `OPTIONS /x HTTP/1.1`. I missed that. In

Re: CORS performance proposal

2015-06-08 Thread Anne van Kesteren
On Tue, Jun 9, 2015 at 6:42 AM, Martin Thomson martin.thom...@gmail.com wrote: The security properties bother me a little. Alt-Svc is showing us that we can't just define a header field like that without some serious analysis. Same goes for a site-wide file. See crossdomain.xml. However,

Re: CORS performance proposal

2015-06-08 Thread Nottingham, Mark
On 9 Jun 2015, at 2:42 pm, Martin Thomson martin.thom...@gmail.com wrote: On 8 June 2015 at 21:30, Nottingham, Mark mnott...@akamai.com wrote: A header denoting site-wide metadata would work for this too, of course, if folks were comfortable with the security properties of doing that (as

Re: Custom Elements: is=

2015-06-08 Thread Travis Leithead
My current understanding of is= is a request for an implementation to plug-in a native element's backing behavior under a custom element name. This feature would otherwise not be available without is=, as custom elements are always generic by design. As Dimitri has noted in the past, I think

Re: CORS performance proposal

2015-06-08 Thread Nottingham, Mark
On 9 Jun 2015, at 2:54 pm, Anne van Kesteren ann...@annevk.nl wrote: On Tue, Jun 9, 2015 at 6:42 AM, Martin Thomson martin.thom...@gmail.com wrote: The security properties bother me a little. Alt-Svc is showing us that we can't just define a header field like that without some serious