Re: [webcomponents]: de-duping in HTMLImports

> Interesting. Why do you need [attribute to opt-out of deduping]?

I don't believe it's *needed* exactly, but we imagined somebody wanting to
import HTML, use it destructively, then import it again.

That may be totally crazy. :)

Scott

On Wed, Apr 10, 2013 at 11:50 AM, Dimitri Glazkov <dglazkov@google.com>wrote:

> On Tue, Apr 9, 2013 at 11:42 AM, Scott Miles <sjmiles@google.com> wrote:
> > Duplicate fetching is not observable, but duplicate parsing and duplicate
> > copies are observable.
> >
> > Preventing duplicate parsing and duplicate copies allows us to use
> 'imports'
> > without a secondary packaging mechanism. For example, I can load 100
> > components that each import 'base.html' without issue. Without this
> feature,
> > we would need to manage these dependencies somehow; either manually, via
> > some kind of build tool, or with a packaging system.
>
> Then I guess I need this spec'd :)
>
> >
> > If import de-duping is possible, then ideally there would also be an
> > attribute to opt-out.
>
> Interesting. Why do you need it?
>
> :DG<
>