- From: Doug Schepers <schepers@w3.org>
- Date: Wed, 25 Nov 2009 14:16:13 -0500
- To: "www-dom@w3.org" <www-dom@w3.org>
Hi, DOM3 Events fans- The minutes for the DOM3 Events telcon of 18 Nov 2009: http://www.w3.org/2009/11/18-webapps-minutes.html Or as text below: [1]W3C [1] http://www.w3.org/ - DRAFT - Web Applications Working Group Teleconference 18 Nov 2009 See also: [2]IRC log [2] http://www.w3.org/2009/11/18-webapps-irc Attendees Present [Microsoft], [IPcaller], Shepazu Regrets Chair SV_MEETING_CHAIR Scribe Travis Contents * [3]Topics * [4]Summary of Action Items _________________________________________________________ <trackbot> Date: 18 November 2009 Travis: Talked to some folks about element-level resize (layout engineers) and based on layout complexity and potential spec vagueness (plus other browsers don't support this), I'd like to not spec this behavior as part of DOM L3 Events. ... Suggested change to spec for resize: proximal event target = Window (only) ... Wanting to ensure Wiki access to create strawman proposal for Faster Mutation Events (discussed with Jonas at TPAC 2009). ... verified that I do have editing access :) ... Got feedback from Microsoft's Office Web Companions: they wanted to have a keyboard language hint for internationalization features (spell/grammer). ... Makes more sense for compositionend events (which tend to be langauge specific). shepazu: Side conversation on shortcomings of not having physical key layout information. ... (re-)discovered keyValues for copy/paste/cut, which solves some common use cases. ... 2 key down sequence: CTRL keyValue + C [key], results in a KeyDown{keyValue:"Control"}, KeyDown{keyValue:"Copy"} Travis: "Labled keys" on my keyboard (Control Key combos): SelectAll, Find, Cut, Copy, Paste, Bold, Underline, Italic ... Non-Function keys (share keyspace as F1-F12): Help, Undo, Redo, New, Open, Close, Reply, Fwd, Send, Spell, Save, Print (Travis/Olli to think about this) Last topic: DOMActivate... Scenario-- user tabs to a link and press enter/space. Event sequence is {KeyboardEvent -> MouseEvent (click) -> Event (DOMActivate). scribe: So this is legacy behavior. ... We can't change this. ... It seems like DOMActivate and click have roughly the same meaning. ... I'll be radical: Let's consider deprecating (like the mutation events) DOMActivate. In its place, make 'click' the new DOMActivate! shepazu: We need to run this by the accessibility community to make sure we're not missing anything. ... Intuition tells me that deprecating DOMActivate will simplify web application development and actually make it simpler to make accessible web applications. <smaug> [5]http://www.w3.org/TR/progress-events/ [5] http://www.w3.org/TR/progress-events/ <smaug> [6]http://mxr.mozilla.org/mozilla-central/source/content/base/src/ns Document.cpp#6145 [6] http://mxr.mozilla.org/mozilla-central/source/content/base/src/nsDocument.cpp#6145 <shepazu> trackbot, end telcon Summary of Action Items [End of minutes] _________________________________________________________
Received on Wednesday, 25 November 2009 19:16:24 UTC