Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2014-02-01 Thread Cameron McCormack
On 22/01/2014 3:09 pm, Boris Zbarsky wrote: Or neither, if desired. In Gecko we don't expose the SVG* properties in IDL at all... We decided against requesting adding an onzoom attribute to GlobalEventHandlers to avoid any complications with whatever solution comes out of the CSSWG who are

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2014-01-22 Thread Erik Dahlström
On Tue, 08 Oct 2013 20:21:08 +0200, Boris Zbarsky bzbar...@mit.edu wrote: On 10/8/13 9:49 AM, Philip Jägenstedt wrote: Gecko has HTMLElement implements GlobalEventHandlers in its IDL,[1] but somewhat surprisingly also SVGElement implements GlobalEventHandlers.[2] Note that in Gecko SVG

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2014-01-22 Thread Boris Zbarsky
On 1/22/14 9:06 AM, Erik Dahlström wrote: In SVG2 most of the events with SVG event name prefixes have been removed[4], e.g SVGLoad is now a plain load, which means they follow the pattern for event handler content attributes. SVGResize, SVGScroll and SVGZoom still remain to be fixed in the

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-09 Thread Philip Jägenstedt
On Wed, Oct 9, 2013 at 12:02 AM, Ian Hickson i...@hixie.ch wrote: On Tue, 8 Oct 2013, Simon Pieters wrote: I think it would be bad to have an IDL attribute without a working content attribute for a given element. That's just confusing. Yeah, that's the main reason I wouldn't put this on

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-09 Thread Erik Dahlstrom
On Wed, 09 Oct 2013 10:53:29 +0200, Philip Jägenstedt phil...@opera.com wrote: ... OK, I hadn't considered that moving this to Element would imply the content attributes being reflected for all namespaces. Even though Blink has the IDL attributes on Element, it looks like the reflection with

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-09 Thread Philip Jägenstedt
On Wed, Oct 9, 2013 at 1:29 PM, Erik Dahlstrom e...@opera.com wrote: On Wed, 09 Oct 2013 10:53:29 +0200, Philip Jägenstedt phil...@opera.com wrote: ... OK, I hadn't considered that moving this to Element would imply the content attributes being reflected for all namespaces. Even though

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Anne van Kesteren
On Tue, Oct 8, 2013 at 4:26 PM, Erik Dahlstrom e...@opera.com wrote: On Tue, 08 Oct 2013 15:49:48 +0200, Philip Jägenstedt phil...@opera.com wrote: 1. Do what Gecko does, even though there's no SVG spec requiring it yet. 2. Just say Element implements GlobalEventHandlers. I would prefer

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Boris Zbarsky
On 10/8/13 11:26 AM, Anne van Kesteren wrote: Have we had success yet making id= and class= super-global? Not sure we should extend the experiment prematurely. In terms of DOM behavior, in Gecko we have been shipping an id attribute on Element.prototype for a good long while now. We haven't

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Boris Zbarsky
On 10/8/13 9:49 AM, Philip Jägenstedt wrote: Gecko has HTMLElement implements GlobalEventHandlers in its IDL,[1] but somewhat surprisingly also SVGElement implements GlobalEventHandlers.[2] Note that in Gecko SVG elements also have event handler content attributes and whatnot. What's your

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Philip Jägenstedt
On Tue, Oct 8, 2013 at 5:26 PM, Anne van Kesteren ann...@annevk.nl wrote: On Tue, Oct 8, 2013 at 4:26 PM, Erik Dahlstrom e...@opera.com wrote: On Tue, 08 Oct 2013 15:49:48 +0200, Philip Jägenstedt phil...@opera.com wrote: 1. Do what Gecko does, even though there's no SVG spec requiring it yet.

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Philip Jägenstedt
On Tue, Oct 8, 2013 at 8:21 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 10/8/13 9:49 AM, Philip Jägenstedt wrote: Gecko has HTMLElement implements GlobalEventHandlers in its IDL,[1] but somewhat surprisingly also SVGElement implements GlobalEventHandlers.[2] Note that in Gecko SVG

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Anne van Kesteren
On Tue, Oct 8, 2013 at 8:35 PM, Philip Jägenstedt phil...@opera.com wrote: I don't know anything about the move of those attributes, has it been attempted in spec and implementation and run into trouble? http://dom.spec.whatwg.org/ is the specification, but I don't think it's been implemented

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Simon Pieters
On Tue, 08 Oct 2013 20:38:48 +0200, Philip Jägenstedt phil...@opera.com wrote: On Tue, Oct 8, 2013 at 8:21 PM, Boris Zbarsky bzbar...@mit.edu wrote: On 10/8/13 9:49 AM, Philip Jägenstedt wrote: Gecko has HTMLElement implements GlobalEventHandlers in its IDL,[1] but somewhat surprisingly

Re: [whatwg] Should onfoo event handler properties be on Element or HTMLElement?

2013-10-08 Thread Ian Hickson
On Tue, 8 Oct 2013, Simon Pieters wrote: I think it would be bad to have an IDL attribute without a working content attribute for a given element. That's just confusing. Yeah, that's the main reason I wouldn't put this on Element if it was up to me. It seems weird to say to everyone around