- From: Rick Byers <notifications@github.com>
- Date: Thu, 17 Dec 2015 08:07:47 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Message-ID: <whatwg/dom/pull/82/r47923459@github.com>
> @@ -1057,6 +1096,25 @@ invoked, must run these steps: > <li><p><a>Dispatch</a> the <var>event</var> and return the value that returns. > </ol> > > +<h3 id=observing-event-listeners>Observing event listeners</h3> > +In general, developers do not expect the presence of an <a>event listener</a> to be > +observable. The impact of an <a>event listener</a> is determined by its <b>callback</b>. > +That is, a developer adding a no-op <a>event listener</a> would not expect it to have > +any side effects. > + > +Unfortunately, some event APIs have been designed such that implementing them > +efficiently requires observing <a>event listeners</a>. For example, sensor APIs which > +enable an underlying device sensor, and touch APIs which can be used to block How about we move this discussion back to [the github issue](https://github.com/RByers/EventListenerOptions/issues/20) so we have a permanent record of the debate? I'm sure it won't be the last time I have it <grin>. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/pull/82/files#r47923459
Received on Thursday, 17 December 2015 16:08:15 UTC