<trackbot> Date: 04 February 2011

<shepazu> http://www.w3.org/2008/webapps/track/products/2

<scribe> scribenick: jrossi2

ISSUE: 140 textInput event as default action of both keydown and keypress

<trackbot> Sorry, bad ISSUE syntax

ISSUE140: textInput as default action of keydown and keypress

<shepazu> issue-140?

<trackbot> ISSUE-140 -- textInput event as default action of both keydown and keypress? -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/140

shepazu: suggestion is that keydown's default action is keypress, and keypress's default action textinput

jrossi: agree

RESOLUTION: make keydown's default action keypress and keypress's default action textinput

<smaug_> I agree

jrossi2: how about mouse events?
... where do we, or should we, define click as default action of mouseup
... I'll investigate current behavior

shepazu: you find that out, and I'll put it in the spec

ISSUE-141?

<trackbot> ISSUE-141 -- IME examples -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/141

jrossi2: this is doable, we ran into this issue
... I can research how we implemented this and send info to the list

<smaug_> ACTION: Olli_Pettay to test mousedown/mouseup default handling (focus and click events at least) [recorded in http://www.w3.org/2011/02/04-webapps-minutes.html#action01]

<trackbot> Sorry, couldn't find user - Olli_Pettay

<shepazu> ACTION: jrossi2 to research how MS implemented issue-141 and send info to the list [recorded in http://www.w3.org/2011/02/04-webapps-minutes.html#action02]

<trackbot> Created ACTION-614 - Research how MS implemented issue-141 and send info to the list [on Jacob Rossi - due 2011-02-11].

ISSUE-142?

<trackbot> ISSUE-142 -- one keydown might fire multiple keypress/textInput events -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/142

<shepazu> ISSUE-142?

<trackbot> ISSUE-142 -- one keydown might fire multiple keypress/textInput events -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/142

RESOLUTION: agree and we'll change that

<shepazu> ISSUE-144?

<trackbot> ISSUE-144 -- exceptions in handlers during event propagation -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/144

jrossi: 2: I think all that's needed here is to specify that exceptions in event handlers don't stop propagtion

smaug_: agree

RESOLUTION: clarify that event propagation still continues even if there are exceptions in event handlers

<shepazu> ISSUE-145?

<trackbot> ISSUE-145 -- Ordering event handlers registered by different means -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/145

jrossi2: it's in the order they are registered, for event attributes it's when the attr is set
... so at parsing, if they are already in the markup

RESOLUTION: event order is in the order of when handlers are registered, whether at parse time or execution time

issue-146?

<trackbot> ISSUE-146 -- Capture-phase listeners invoked on targets -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/146

<smaug_> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-EventTarget-addEventListener

smaug_: this is fixed

issue-147?

<trackbot> ISSUE-147 -- re-dispatching an event that already has its flow started -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/147

RESOLUTION: clarify that this is in the spec and get a response from sergey

<shepazu> ISSUE-153?

<trackbot> ISSUE-153 -- Converting wheel events to mousewheel and DOMMouseScroll -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/153

RESOLUTION: clarify platforms can vary, update example code, and mark just as informative

<shepazu> ISSUE-154?

<trackbot> ISSUE-154 -- Clarify diagonal wheel deltas on wheel events -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/154

jrossi2: Windows has separate message for HSCROLL and VSCROLL, so I'm mostly certain we fire these separately

smaug_: OSX may allow events to fire with both axes

RESOLUTION: clarify that this environment specific

<shepazu> ISSUE-157?

<trackbot> ISSUE-157 -- Problems with initKeyboardEvent -- raised

<trackbot> http://www.w3.org/2008/webapps/track/issues/157

<shepazu> trackbot, end telcon

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)

Found ScribeNick: jrossi2
Inferring Scribes: jrossi2

WARNING: No "Topic:" lines found.

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

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

Found Date: 04 Feb 2011
Guessing minutes URL: http://www.w3.org/2011/02/04-webapps-minutes.html
People with action items: jrossi2 olli_pettay

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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