W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2010

Re: No events are of type Event

From: Doug Schepers <schepers@w3.org>
Date: Wed, 03 Mar 2010 04:47:43 -0500
Message-ID: <4B8E303F.5040302@w3.org>
To: www-dom@w3.org
Hi, Folks-

I'm trying to decide how to resolve this issue.  There was a decision 
made to change some of the event types from the Event interface to the 
UIEvent interface, but I cannot find the rationale now.

The difference between these two interfaces is that UIEvent adds two 
* UIEvent.view
* UIEvent.detail

Neither of these seems especially critical for any of the event types 
currently defined as UIEvents, with the exception of DOMActivate, which 
used UIEvent.detail as described fancifully in DOM2 Events:

The activate event occurs when an element is activated, for instance, 
thru a mouse click or a keypress. A numerical argument is provided to 
give an indication of the type of activation that occurs: 1 for a simple 
activation (e.g. a simple click or Enter), 2 for hyperactivation (for 
instance a double click or Shift Enter).

(Somehow this text got lost in DOM3 Events... I reckon I should 
reinstate it, even if we are deprecating the event type?)

I prefer the spec organization as it is, but I'm having a hard time 
justifying why any of these events would belong explicitly in either 
Event or UIEvent... can someone supply a rationale?

Olli Pettay wrote (on 1/31/10 1:21 PM):
> 5.1.1
> - I don't remember or know why scroll and resize were changed from
> being Events to be UIEvent
> 5.1.1 and 5.2.1 are inconsistent. The first one says that load etc
> implements Event (like it is in DOM 2), but latter one says that
> load is an UIEvent.
> I don't understand the comment "UIEvent if generated from a user
> interface, Event otherwise." Why not just always Event.

Travis Leithead wrote (on 3/1/10 12:40 PM):
> In looking through the table:
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-types-list
> I noticed that none of the events that are shown as DOM Interface
> “Event” are actually defined to be of type Event, rather they all seem
> to be listed under UIEvent. Is the table right, or the definition of the
> events?

Jacob Rossi wrote (on 3/1/10 2:21 PM):
> The ones listed as Event are in fact UIEvent if the source of the event
> was the user interface. In the case that the event occurs from another
> source (e.g., an error event from, say, script execution) then it just
> takes on the Event interface. This is the case for error, load, unload,
> and select. Though, admittedly I can't come up with a scenario where
> select originates from something other than UI.
> Perhaps, the table should list both UIEvent and Event as the interfaces.
> Or perhaps just the most common case, which for many of these would be
> UIEvent rather than Event.

-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Wednesday, 3 March 2010 09:47:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:36:56 UTC