[Bug 27823] We should consider dropping [NoInterfaceObject] from XMLHttpRequestEventTarget

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27823

--- Comment #20 from Jonas Sicking <jonas@sicking.cc> ---
(In reply to Anne from comment #18)
> (In reply to Jonas Sicking from comment #16)
> > I think the simplest solution is to simply get rid of
> > XMLHttpRequestEventTarget and add the corresponding on* properties to the
> > XMLHttpRequestUpload and XMLHttpRequest interfaces. That's essentially how
> > the rest of the DOM works.
> 
> Not really. If we can't use inheritance we use mixins.

Lots of interfaces have onfoo's directly on them. Like Window and WebSocket.
But yes, I'd be fine with using mixin's too.

> > The XMLHttpRequestEventTarget interface seems
> > like a feature without use cases.
> 
> If you want to extend both XMLHttpRequest and XMLHttpRequestUpload it's the
> way to go.

What's the use case?

(In reply to Olli Pettay from comment #19)
> (In reply to Jonas Sicking from comment #17)
> > onfoo isn't really functionality. It's just syntax sugar.
> 
> Unfortunately onfoo can be very much more than that, as in case of
> MessagePort's onmessage.

Sure, but that's not the case here, no?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 16 January 2015 01:42:50 UTC