See also: IRC log
<trackbot> Date: 26 March 2008
Zakim: who is on the phone
<shepazu> Scribe: Olli Pettay
<shepazu> scribeNick: smaug
DS: (the diagram does look right
... going through the diagram
TL: will look how this work on IE
DS: everybody should look how
"their" browser work
... I'm happy modify the diagram some more
... the middle textInput, currently there isn't repeat in DOM. We should probably add it
... repeat="true" might only happen on character keys
... not sure where IME should go
DS: going through the actions
OP: I don't think I can take actions officially yet
DS: TL any progress on that action?
<Travis> I'll try to find my old test and post it.
AE: I was going to work on mousewheel event today but got some email from smaug about that
DS: reviewing the email
... It shouldn't be hard to test if wheelDelta is zero
... the new event wouldn't break existing pages
the previous proposal http://lists.w3.org/Archives/Public/public-webapi/2006May/0029.html
might be the best compromise
... but need to specify the order of the events
DS: everybody seem to be ok with
the wheel event
... I'll modify the wheel event proposal
CM: it could help SVg
DS: we're getting rid of the mega-multi-mousewheel
TL: what the HTML4 event listener behaviour is vs DOM event listeners
OP: we should look at HTML5
<ohunt> sprry for being late
<shepazu> very sprry indeed
<shepazu> gonna call in?
<Travis> HTML5 on events: http://www.w3.org/html/wg/html5/#events
TL: IE keeps separete list for HTML event listeners
TL: html event listeners fires first
<shepazu> "When scripting is enabled, all event handler attributes on an element, whether set to null or to a function, must be registered as event listeners on the element, as if the addEventListenerNS() method on the Element object's EventTarget interface had been invoked when the element was created, with the event type (type argument) equal to the type described for the event handler attribute in the list above, the namespace (namespaceURI argument) set to null,
TL: could set listener using html attribute and then remove using removeEventListener?
DS: SVG has the same issue
... TL, are you willing to change how IE does this?
TL: we have things to do to get normal event to work. but yes, we could change it
should there be some way to enumerate event listeners
DS: goes to the point that there
should be only one list of listeners
... the only issue is removing the listener
... if parameters are all the same, removing listener could remove the attribute from DOM?
<scribe> ACTION: Travis Test addEventListener vs onFoo attribute [recorded in http://www.w3.org/2008/03/26-webapi-minutes.html#action01]
<trackbot> Created ACTION-266 - Test addEventListener vs onFoo attribute [on Travis Leithead - due 2008-04-02].
TL: could propose something for enumerating listeners
DS: don't want to add too many things to DOM 3 Events
<shepazu> ACTION: Travis to make proposal for event iterator [recorded in http://www.w3.org/2008/03/26-webapi-minutes.html#action02]
<trackbot> Created ACTION-267 - Make proposal for event iterator [on Travis Leithead - due 2008-04-02].
DS: back to the key flow
OH: not sure you always get a
... because of IME
DS: should be noted in the spec that one should not rely on the keypress
<oliver> The problem is that the keypress event has a more or lesss 1:1 correspondaence to WM_CHAR
<oliver> which other platforms don't actually have
DS: DOM 3 keyevents would be the
model for the web
... I'm looking at the most implementable
OH: someone else to give feedback what webkit does
DS: would be great to get
feedback from everyone
... will have some proposal for mobile keys next week
<shepazu> "Command-= and Command-Shift-= and Command-+ are, or are not, the same key on my
<shepazu> keyboard, and I don't know how to write content that handle Command-Minus and
<shepazu> Command-Plus independent of what the layout actually is, especially given that I
<shepazu> might also want to distinguish Command-= and Command-Shift-= sometimes."
DS: is this really a serious
... you get events for all the keys
OH: IME may affect to the input?
DS: specifying IME handling
should take care of this
... authors should rely on keydown and textinput
<scribe> ACTION: TL to test zoom in/out on keyboard [recorded in http://www.w3.org/2008/03/26-webapi-minutes.html#action03]
<trackbot> Created ACTION-268 - Test zoom in/out on keyboard [on Travis Leithead - due 2008-04-02].
DS: something wrong in my model...
TL: many laptops have customizable keys
should we have more generic input events?
<shepazu> trackbot, end telcon
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: firstname.lastname@example.org/ / Found Scribe: Olli Pettay Found ScribeNick: smaug Default Present: Doug, Carmelo, aemmons, [Microsoft], smaug, Travis, +1.408.996.aaaa Present: Doug Carmelo aemmons [Microsoft] smaug Travis +1.408.996.aaaa Agenda: http://www.w3.org/2008/webapps/wiki/26_Mar_2008 Found Date: 26 Mar 2008 Guessing minutes URL: http://www.w3.org/2008/03/26-webapi-minutes.html People with action items: tl travis WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]