[whatwg] Additional onxxxx event attributes for DOM Level3 Events

David Flanagan david at davidflanagan.com
Tue Nov 30 21:11:53 PST 2010

On 11/30/2010 03:18 PM, Garrett Smith wrote:
> On 11/30/10, Ian Hickson<ian at hixie.ch>  wrote:
>> On Mon, 16 Aug 2010, Hajime Morita wrote:
>>> I noticed that some events which are defined in DOM Level3 Events [1]
>>> don't have
>>> associated HTML attributes.
>>> For example, "keypress" event has associated "onkeypress" attribute.
>>> But "focusin" event doesn't have "onfocusin" attribute.
> It does in IE.
>>> Here is a list:
>>> * wheel event
> `onmousewheel`? That's in IE.

The "wheel" event is a different, generalized, version of the 
"mousewheel" event.  As far as I know, no one has implemented it yet.

>>> * textInput event
> Following the convention of lc for event handler properties, `ontextinput`?

Last I checked, the DOM3 spec had changed "textInput" to "textinput". 
Safari and Chrome fire textInput (with a capital I) events but do not 
currently define an attribute for it.

>>> * focusin event
>>> * focusout event
> Those are in IE.
>>> * compositionstart event
>>> * compositionupdate event
>>> * compositionend event
>>> * DOMXxxx events

Last I checked, the DOMxxx events were all basically being deprecated in 
D3E.  So it would be bad to standardize attributes for those, I think.


>>> I think these events should have associated attributes defined.
>>> DOM mutation events might be better to skip due to its long name and rare
>>> usage.
>>> But it's just a preference and not a strong opinion.

>> I'm happy to add new event handler attributes, but not to add them just
>> based on completeness. New features are added based on either use cases
>> (i.e. problems that authors or users are facing), or compatibility (i.e.
>> things that browsers already do). If there are specific events for which
>> event handler attributes would be useful, I encourage you to request those
>> specifically, describing either the relevant use cases or citing the
>> existing implementations, as appropriate.
> The reason event handler properties are useful is that they can be
> detected. A program can make a fair assessment as to whether the
> element supports the event handler in question and how to handle the
> case where that isn't supported.
> That isn't possible with event target; there is no such,
> `object.generatesEvent`, nor will there be in D3E, according its
> author.
> Garrett

More information about the whatwg mailing list