Re: [webcomponents]: Moving custom element callbacks to prototype/instance from Dimitri Glazkov on 2013-03-08 (public-webapps@w3.org from January to March 2013)

From: Dimitri Glazkov <dglazkov@google.com>
Date: Fri, 8 Mar 2013 09:48:49 -0800
To: public-webapps <public-webapps@w3.org>
Cc: Scott Miles <sjmiles@google.com>, Elliott Sprehn <esprehn@google.com>, Steve Orvell <sorvell@google.com>, Daniel Buchner <daniel@mozilla.com>, Adam Klein <adamk@google.com>, Hajime Morrita <morrita@google.com>, Blake Kaplan <mrbkap@mozilla.com>, William Chen <wchen@mozilla.com>
Message-ID: <CADh5Ky09oYkycz7KOT5JnfFW1g96_2nJ37DpOr=iZS-hAc4g-Q@mail.gmail.com>

On Wed, Mar 6, 2013 at 1:55 PM, Dimitri Glazkov <dglazkov@google.com> wrote:

> Cons:
> * The callbacks now hang out in the wind as prototype members. Foolish
> people can invoke them, inspectors show them, etc.

This con could get uncomfortably exciting if we try building HTML
elements with custom elements. For example, today all WebKit forms
controls use the equivalent of the insertedCallback to hook up with
the <form> element. We could make these callbacks non-configurable so
that enthusiastic authors don't get any ideas, but these same authors
could still call them and wreak all kinds of havoc.

:DG<

Received on Friday, 8 March 2013 17:49:21 UTC