On Thu, Jan 15, 2015 at 6:43 PM, Ryosuke Niwa <rn...@apple.com> wrote:
> > > On Jan 14, 2015, at 12:52 PM, Dimitri Glazkov <dglaz...@google.com> > wrote: > > > > FWIW, I think that element upgrade is sort of fundamental to the > usefulness of custom elements. In a world where most scripts are > non-blocking (that's hopefully the modern world we should aim for), I'll > effectively expect to walk the tree anyway. > > Allowing loading scripts asynchronously, including ones that define custom > elements, is one thing; automatically resolving script dependencies for > custom elements is another. What are the "script dependencies for custom elements" here? > When an author imports a ES6 module, we don't create a fake object which > gets resolved later by rewriting its prototype. > These are two completely different things, right? In one situation, you are dealing with HTML Parser and blocking thereof. In another, there's no such concern. :DG<
