Re: [webcomponents]: Moving custom element callbacks to prototype/instance

>From an implementors perspective:

Putting such callbacks on the prototype object means that it can be
changed, or even can be added after the element registration. This is
different from a function parameter, which we can consider as a snapshot.

One consequence is that it will become harder to cache (including negative
cache) these values. We need to traverse the prototype chain in C++, which
is typically slower than doing it in JS, on every lifecycle event. Or we
need to invent something cool to make it fast.

On Thu, Mar 7, 2013 at 7:29 AM, Dimitri Glazkov <> wrote:

> On Wed, Mar 6, 2013 at 2:20 PM, Scott Miles <> wrote:
> > That's the ultimate goal IMO, and when I channel Alex Russell (without
> > permission). =P
> Don't we already have Fake Alex for that (
> :DG<


Received on Thursday, 7 March 2013 00:04:25 UTC