Web Applications Working Group Teleconference

18 Nov 2009

See also: IRC log


[Microsoft], [IPcaller], Shepazu




<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> http://www.w3.org/TR/progress-events/

<smaug> http://mxr.mozilla.org/mozilla-central/source/content/base/src/nsDocument.cpp#6145

<shepazu> trackbot, end telcon

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/11/18 21:13:21 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: Travis
Inferring Scribes: Travis

WARNING: No "Topic:" lines found.

Default Present: [Microsoft], [IPcaller], Shepazu
Present: [Microsoft] [IPcaller] Shepazu

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 18 Nov 2009
Guessing minutes URL: http://www.w3.org/2009/11/18-webapps-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report

[End of scribe.perl diagnostic output]