W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [webcomponents]: What callbacks do custom elements need?

From: Dimitri Glazkov <dglazkov@chromium.org>
Date: Tue, 12 Mar 2013 09:51:39 -0700
Message-ID: <CADh5Ky2kYO5r+2rZKKNZh7xE9qB_H1baJWsNcqkjPpqJN+h0Dg@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, public-webapps <public-webapps@w3.org>
On Tue, Mar 12, 2013 at 1:42 AM, Jonas Sicking <jonas@sicking.cc> wrote:

> On Mon, Mar 11, 2013 at 5:45 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> > On 3/11/13 5:18 PM, Elliott Sprehn wrote:
> >>
> >> "inserted" and "removed" can probably be end of micro task, but
> >> attributeChanged definitely needs to be synchronous to model the
> >> behavior of <input type> where changing it from X to Y has an immediate
> >> effect on the APIs available (like stepUp).
> >
> > Hmm.  That's a good point.  We should rope in Jonas and Olli on this bit.
> >
> > As long as it's ok to call attributeChanged right before the return from
> the
> > attribute mutator, this seems to be a reasonable thing to me.
> There's lots of tricky aspects of specifying this. For example if
> WebComponents support attribute forwarding (I haven't checked if it
> does) then that means that all attributes will be forwarded before any
> of the attribute-changed callbacks can run.

There's no concept of attribute forwarding in custom elements. If we do
bring something like this in, it'll be built on top of theses callbacks, I
hope -- a declarative syntax to match the imperative API.

Received on Tuesday, 12 March 2013 16:52:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:59 UTC