On Thu, Apr 11, 2013 at 4:41 PM, Scott Miles sjmi...@google.com wrote:
On Thu, Apr 11, 2013 at 12:33 AM, Angelina Fabbro
angelinafab...@gmail.com wrote:
I don't believe it's *needed* exactly, but we imagined somebody wanting
to import HTML, use it destructively, then import it again.
Can you guys file a bug so that we remember?
:DG
On Mon, Apr 15, 2013 at 8:09 PM, Dominic Cooney domin...@google.com wrote:
On Thu, Apr 11, 2013 at 4:41 PM, Scott Miles sjmi...@google.com wrote:
On Thu, Apr 11, 2013 at 12:33 AM, Angelina Fabbro
angelinafab...@gmail.com wrote:
I don't
I don't believe it's *needed* exactly, but we imagined somebody wanting
to import HTML, use it destructively, then import it again.
That does sound totally crazy. Can you give an example as to what someone
might want to do with this? Maybe it's not totally crazy and I'm just not
being creative
On Thu, Apr 11, 2013 at 12:33 AM, Angelina Fabbro
angelinafab...@gmail.comwrote:
I don't believe it's *needed* exactly, but we imagined somebody wanting
to import HTML, use it destructively, then import it again.
That does sound totally crazy. Can you give an example as to what someone
On Tue, Apr 9, 2013 at 11:42 AM, Scott Miles sjmi...@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
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
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
feature.
:DG
On Tue, Apr 9, 2013 at 10:53 AM, Scott Miles sjmi...@google.com wrote:
When writing
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.
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.
WDYT?
On Tue, Apr 9, 2013 at 2:42 PM, Scott Miles sjmi...@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
10 matches
Mail list logo
