Re: [webcomponents]: de-duping in HTMLImports

The trick here is to figure out whether de-duping is observable by the
author (other than as a performance gain). If it's not, it's a
performance optimization by a user agent. If it is, it's a spec


On Tue, Apr 9, 2013 at 10:53 AM, Scott Miles <> wrote:
> When writing polyfills for HTMLImports/CustomElements, we included a
> de-duping mechanism, so that the same document/script/stylesheet is not (1)
> fetched twice from the network and (2) not parsed twice.
> But these features are not in specification, and are not trivial as design
> decisions.
> Scott

Received on Tuesday, 9 April 2013 19:17:44 UTC