See also: IRC log
<trackbot> Date: 29 July 2009
<shepazu> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
<shepazu> scribeNick: MSJacob
shepazu: seen content w/
DOMFocusIn and DOMFocusOut, if we can get SVG implementors to
say it's ok to deprecate these, I would say that the SVG spec
could (a) add an errata that says authors should use DOM3
Events focus and blur events
... problem is that adding features to a recommendation is not
supposed to happen, but that may not be what is needed
... we could probably get away with simply noting a suggestion
to use D3E focus/blur events
... content could be updated
... I'll bring this up with SVG wg next week
<dand> gday
shepazu: what about content not working in the browsers? but if this is what browser implementors want, then this is probably the best solution
<smaug> +1.617.761.6200
<smaug> 3663
<dand> cheers
shepazu: I'm concerned if people remove DOMActivate, there may be content that breaks
<shepazu> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-TextEvent
MSJacob: What can input mode multimodal be used for?
shepazu: combos of input methods (ex, voice "meet me here" then click on a map)
smaug: What is DOM_INPUT_METHOD_OPTION?
shepazu: select an option and it generates a text event (ex, xforms)
MSJacob: What about script-generated text inputs?
shepazu: I considered DOM_INPUT_SCRIPT, but that seems less descriptive. But thinking further, I might want to add it. What do other people think?
MSJacob: Test automation is free to fire textInput with whatever inputMethod it wants. But simply generating a text insertion via script should probably have its own input method.
smaug: No particular opinion.
shepazu: I'
... I'll add it in and we'll see.
shepazu: I added them in but I might deprecate them.
smaug: Add it and deprecate it? why?
shepazu: Included to provide context for supporting IE, but deprecated.
MSJacob: Including it simply for
documentation of IE7/8 support doesn't make sense since IE
doesn't support DOM events. But if they solve a different
scenario, then they should be included.
... I may have usage data for sites in IE8 that I can send
out.
<shepazu> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-event-mouseenter
<annevk> (link doesn't work)
<annevk> (btw, I read that text earlier today and I'm not sure event target is the term you want to use, isn't it about the node the listener is registered on?)
MSJacob: I think there's significant asks for this on the web. Specifically, the best argument is they are the equivelant of :hover pseudo-class.
smaug: the wording may not be exactly correct.
MSJacob: yes, the "propagation path must end at the event target element" is not exactly accurate
shepazu: we should have a more detailed discussion on the mailing list
shepazu: composition events, and
detail of keyboard event behaviors
... no meeting next week, I'm out of town
dand: still some open issues with
composition events
... some proposed API solutions, but not 100% sure....requires
more discussion
shepazu: I'll put this in the
spec and we'll keep on discussing
... maybe I'll make a wiki page that people can edit for open
issues
... I've been talking to wacom about influencing tablet/touch
events
<shepazu> trackbot, stop telcon
<trackbot> Sorry, shepazu, I don't understand 'trackbot, stop telcon'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
<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: MSJacob Inferring Scribes: MSJacob Default Present: [Microsoft], Shepazu, smaug, dand Present: [Microsoft] Shepazu smaug dand Found Date: 29 Jul 2009 Guessing minutes URL: http://www.w3.org/2009/07/29-webapps-minutes.html People with action items:[End of scribe.perl diagnostic output]