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

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 8 Mar 2013 10:49:14 -0800
Message-ID: <CA+c2ei8g1uy_D_7PHGm2ga0SBesQs-YEP7KFihiFRCUt_oyziQ@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>
Cc: William Chen <wchen@mozilla.com>, Daniel Buchner <daniel@mozilla.com>, Hajime Morrita <morrita@google.com>, Elliott Sprehn <esprehn@google.com>, Blake Kaplan <mrbkap@mozilla.com>, public-webapps <public-webapps@w3.org>, Steve Orvell <sorvell@google.com>, Scott Miles <sjmiles@google.com>
On Mar 6, 2013 2:07 PM, "Dimitri Glazkov" <dglazkov@google.com> wrote:
>
> Here are all the callbacks that we could think of:
>
> * readyCallback (artist formerly known as "create") -- called when the
> element is instantiated with generated constructor, createElement/NS
> or shortly after it was instantiated and placed in a tree during
> parser tree construction
>
> * attributeChangedCallback -- synchronously called when an attribute
> of an element is added, removed, or modified

This will have many of the same problems that mutation events had. I
believe we want to really stay away from synchronous.

So yes, this looks dangerous and crazy :-)

/ Jonas
Received on Friday, 8 March 2013 18:49:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:58 GMT