Re: [webcomponents]: First stab at the Web Components spec

On Fri, Mar 8, 2013 at 1:19 AM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Thu, Mar 7, 2013 at 11:25 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
>> Please look over it. I look forward to your eagle-eyed insights in the
>> form of bugs and emails.
>
> You try to monkey patch the obtain algorithm but in doing so you
> invoke a different fetch algorithm. One which does not expose
> resources as CORS-cross-origin. Also, for rel=component tainted
> resources make no sense, so we should only use "No CORS" in
> combination with "fail".

That wasn't my intent. I'll look over that again. Thanks!

>
> Why is Component not simply a subclass of Document? If you already
> have a Document object you might as well use that directly...

I just mirrored LinkStyle
(http://dev.w3.org/csswg/cssom/#the-linkstyle-interface) here. Given
that  document already has URL, you're right -- I don't need the
Component interface at all. LinkComponent could just have a content
attribute that returns Document. Also, there's no need for
sub-classing anything. Components are just documents.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21225

>
> Also, it sounds like this specification should be titled "Fetching
> components" or some such as that's about all it defines. Can't we just
> put all the component stuff in one specification? I find the whole
> organization quite confusing.

Components don't directly correlate with custom elements. They are
just documents that you can load together with your document. With
things like multi-threaded parser, these are useful on their own, even
without custom elements.

:DG<

Received on Friday, 8 March 2013 18:04:13 UTC