Re: [clipboard] kill onbefore* events?

On Wed, Mar 9, 2016 at 2:29 PM, Hallvord Reiar Michaelsen Steen
<> wrote:
> In my personal (and humble) opinion it's not actually a benefit for
> developers to have only one event that will fire a lot and indicate
> lots of different things. I accept that library authors want a
> convenient "point of overview" regarding what happens in the DOM (but
> wasn't mutation observers supposed to do that job?). However, making
> one single event type carry lots of different information and adding
> stuff like clipboardData and/or dataTransfer (because drag-and-drop
> changes the DOM too, right?) to the InputEvent interface seems like we
> force authors to
> 1) Write code with lots of if(e.eventType === foo) and
> switch(e.eventType) branching, which is hard to read
> 2) Debug code that gets run a lot all the time - event loops that fire
> often are annoying when debugging

I strongly agree with this. We should not design another
XMLHttpRequest readystatechange event disaster.


Received on Wednesday, 9 March 2016 14:13:42 UTC