ISSUE-63 - Public View
Should Window 1.0 drop the arguably redundant requirment on UIEvent.view?
- State:
- CLOSED
- Product:
- Window
- Raised by:
- Maciej Stachowiak
- Opened on:
- 2006-04-04
- Description:
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.
- Related emails:
- ISSUE-63: Should Window 1.0 drop the arguably redundant requirment on UIEvent.view? (from dean+cgi@w3.org on 2006-04-04)
- Re: ISSUE-63: Should Window 1.0 drop the arguably redundant requirment on UIEvent.view? (from annevk@opera.com on 2006-04-06)
- Re: Window: rewrite Navigation section, added History (from xmlizer@gmail.com on 2006-05-01)
- Minutes, face to face meeting (from chaals@opera.com on 2006-05-15)
Note: Some of these links may be accessible only to W3C Members.
Related notes:
No additional notes.