W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

ISSUE-63: Should Window 1.0 drop the arguably redundant requirment on UIEvent.view?

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Tue, 4 Apr 2006 03:22:33 +0000 (GMT)
To: public-webapi@w3.org
Message-Id: <20060404032233.ED48166367@dolph.w3.org>


ISSUE-63: Should Window 1.0 drop the arguably redundant requirment on UIEvent.view?

http://www.w3.org/2005/06/tracker/webapi/issues/63

Raised by: Maciej Stachowiak
On product: Window

Currently the spec says:

When an event implementing the <code>UIEvent</code> interface [DOM3EV] is dispatched on any 
node in a <code>Document</code> presented in a <term>browsing context</term>, the value of the 
<code>view</code> attribute of the event MUST be the <code>Window</code> object where the 
user originated the event.

This is arguably redundant with the requirement that views must implement the Window interface and 
the similar DOM Level 2 Views requirement about UIEvent:

   A UIEvent typically occurs upon a view of a Document (e.g., a mouse click on a browser frame 
rendering a particular Document instance). A UIEvent has an AbstractView associated with it which 
identifies both the particular (implementation-dependent) view in which the event occurs, and the 
target document the UIEvent is related to.

DOM Level 3 Events also says:

  view of type views::AbstractView, readonly 
      The view attribute identifies the AbstractView from which the event was generated.

Given this, we should probably drop the requirement for Window.
Received on Tuesday, 4 April 2006 03:23:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT