Re: [webcomponents] HTML Imports

On Wed, 04 Dec 2013 18:58:10 +0100, Scott Miles <> wrote:

>> seems a specification that seems really pushed/rushed
> Since my team (Polymer) has been working with imports in practice for a
> year-and-a-half (100% public and open-source, btw) this seems a strange
> conclusion.

As Bjoern pointed out, this functionality is something we have been trying  
to get on the web for most of the history of the web. And I think it is  
fair to say that we have often pushed to get something accepted. We're  
still pushing - it would be useful to solve this longstanding problem.

I don't know if that equates to "rushed". This is discussed elsewhere, and  
I don't think it's a very fruitful discussion.

> But this is only my perspective, I'm still a standards n00b I suppose.
> In any case, I codified the concepts that our team has been espousing in  
> a document here:
> The aim of this document was to address some of the questions around
> pragmatic operation of the spec as we see it.

Thanks. This is helpful. More perspectives from different kinds of people  
who have tried to use Web components may be important contribution in  
deciding whether we have it right enough.



> Scott
> On Wed, Dec 4, 2013 at 4:32 AM, Anne van Kesteren <>  
> wrote:
>> On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma <> wrote:
>> > I would say though that I get the feeling that Web Components seems a
>> > specification that seems really pushed/rushed and I worry that might
>> > lead to some poor design decisions whose side effects will be felt by
>> > developers in the future.
>> I very much share this sentiment.
>> --

Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex         Find more at

Received on Thursday, 5 December 2013 10:23:18 UTC