Re: [webcomponents] Cross origin HTML imports
On Thu, Oct 24, 2013 at 1:38 AM, Hajime Morrita morr...@google.com wrote: OK, I will refer the fetch section in HTML spec then. I think you misunderstood, http://fetch.spec.whatwg.org/#fetching is the entry point. -- http://annevankesteren.nl/
Re: [webcomponents] Cross origin HTML imports
Oh I see. Thanks for the clarification. On Thu, Oct 24, 2013 at 5:54 PM, Anne van Kesteren ann...@annevk.nl wrote: On Thu, Oct 24, 2013 at 1:38 AM, Hajime Morrita morr...@google.com wrote: OK, I will refer the fetch section in HTML spec then. I think you misunderstood, http://fetch.spec.whatwg.org/#fetching is the entry point. -- http://annevankesteren.nl/ -- morrita
RfC: LCWD of Custom Elements; deadline November 21
This is a Request for Comments for the Last Call Working Draft of Custom Elements: http://www.w3.org/TR/2013/WD-custom-elements-20131024/ If you have any comments, please send them to public-webapps @ w3.org by November 21 using a Subject: header of [custom-elements] -Thanks, AB
Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
On Wed, Oct 9, 2013 at 2:54 PM, Elliott Sprehn espr...@gmail.com wrote: shadowRoot.appendChild(new Text()) should probably throw an exception. Woke up in the middle of the night and realized that throwing breaks ShadowRoot.innerHTML (or we'll have to add new rules to hoist/drop text nodes in parsing), which sounds bad. :DG
Re: [webcomponents]: Allowing text children of ShadowRoot is a bad time
On Thursday, October 24, 2013, Dimitri Glazkov wrote: Woke up in the middle of the night and realized that throwing breaks ShadowRoot.innerHTML (or we'll have to add new rules to hoist/drop text nodes in parsing), which sounds bad. innerHTML would end up re-throwing the same exception, unless you special-cased parsing. innerHTML throwing is somewhat unexpected though. -- http://annevankesteren.nl/
