W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2015

Re: Callback when an event handler has been added to a custom element

From: Justin Fagnani <justinfagnani@google.com>
Date: Fri, 6 Nov 2015 11:28:36 -0800
Message-ID: <CAEKsHmArrGAJE9J+vDjs+-8jF9opqDCdpmEKB2Qe5sYeJkH=_g@mail.gmail.com>
To: Travis Leithead <travis.leithead@microsoft.com>
Cc: Mitar <mmitar@gmail.com>, public-webapps <public-webapps@w3.org>
You can also override addEventListener/removeEventListener on your element.
My concern with that, and possibly an event listener change callback, is
that it only works reliably for non-bubbling events.

On Thu, Nov 5, 2015 at 4:16 PM, Travis Leithead <
travis.leithead@microsoft.com> wrote:

> Interesting. Alternatively, you can add .onwhatever handlers, as well as
> define your own overload of addEventListener (which will be called instead
> of the EventTarget.addEventListener method). That way you can capture all
> attempts at setting events on your element.
>
> -----Original Message-----
> From: Mitar [mailto:mmitar@gmail.com]
> Sent: Thursday, November 5, 2015 4:05 PM
> To: public-webapps <public-webapps@w3.org>
> Subject: Callback when an event handler has been added to a custom element
>
> Hi!
>
> We are using message ports to communicate with our logic and are wrapping
> the API into a custom element. The issue is that we would like to call
> start on a message port only after user has registered an event handler on
> the custom element instance. But it seems there is no way to get a callback
> when an event handler is added.
>
> So I am suggesting that there should be a callback every time an event
> listener is added to a custom element (and possibly one when removed).
>
>
> Mitar
>
> --
> http://mitar.tnode.com/
> https://twitter.com/mitar_m
>
>
Received on Friday, 6 November 2015 19:29:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:58 UTC