Use EventHandler type instead of EventListener for event handler attributes

Use EventHandler type instead of EventListener for event handler attributes

Distinguish in the IDL the HTML EventHandler attributes and DOM EventListener
types added via addEventListener() method to match the specifications:
http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#eventhandler
http://dom.spec.whatwg.org/#eventlistener

This makes our IDL closer to the specifications but there is no web-exposed
behavior change with this patch. In the future, however, we may consider
supporting only JS Functions (not objects with handleEvent() method) as
input for EventHandler attributes to match the specification.

R=haraken

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=155702

[haraken, 2013-08-07 12:47:38]

LGTM

[arv (Not doing code reviews), 2013-08-07 13:35:10]

LGTM

WOW, I didn't know we allowed something as crazy broken as:

document.onclick = {
  handleEvent: function(e) {
    console.log(this, e);
  }
};

I've never ever seen anyone ever use this outside addEventListener.

Is there a bug for this?

[do-not-use, 2013-08-07 13:40:21]

On 2013/08/07 13:35:10, arv wrote:
> LGTM
> 
> WOW, I didn't know we allowed something as crazy broken as:
> 
> document.onclick = {
>   handleEvent: function(e) {
>     console.log(this, e);
>   }
> };
> 
> I've never ever seen anyone ever use this outside addEventListener.
> 
> Is there a bug for this?

Not that I know of (I searched quickly but did not find any). I just found out
about the API mismatch when working on this CL.
I am happy to file one and work on this in a follow-up CL though.

[arv (Not doing code reviews), 2013-08-07 14:01:39]

On 2013/08/07 13:40:21, Christophe Dumez wrote:
> On 2013/08/07 13:35:10, arv wrote:
> > LGTM
> > 
> > WOW, I didn't know we allowed something as crazy broken as:
> > 
> > document.onclick = {
> >   handleEvent: function(e) {
> >     console.log(this, e);
> >   }
> > };
> > 
> > I've never ever seen anyone ever use this outside addEventListener.
> > 
> > Is there a bug for this?
> 
> Not that I know of (I searched quickly but did not find any). I just found out
> about the API mismatch when working on this CL.
> I am happy to file one and work on this in a follow-up CL though.

https://code.google.com/p/chromium/issues/detail?id=269520

[commit-bot: I haz the power, 2013-08-07 16:32:40]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ch.dumez@sisa.samsung.com/22581002/1

[commit-bot: I haz the power, 2013-08-07 18:19:44]

Change committed as 155702