W3C

- DRAFT -

Web Applications Working Group Teleconference

27 Jan 2010

See also: IRC log

Attendees

Present
Shepazu, [Microsoft], Olli_Pettay
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Travis

Contents


<trackbot> Date: 27 January 2010

<smaug> oops

<smaug> just a second..

<shepazu> http://dev.w3.org//2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-flow-activation

<scribe> scribe: Travis

<scribe> scribeNick: Travis

Updated Draft

shepazu: clarified the section on activation behavior.
... wrote a new section on "trusted events"
... also added some prose about syncronous vs. asynchronous events
... is the Trusted event section accurate?

You're missing dispatchEvent -- it'll always create un-trusted events

Internationalization

shepazu: Need to examine whether the convertKeyValue API is needed.
... I will be meeting with internationalization folks to follow up on the scenarios.
... Also, want to figure out what the appropriate terminology is for the "character" returned by the 'key' API.

select element context info issue

Travis: We have an issue about how to get the context from a select event.

shepazu: Don't think this is a blocking issue.

<scribe> ACTION: shepazu Ask SVG and HTML WGs what their recommended approach is for getting the selected text (related to select event) [recorded in http://www.w3.org/2010/01/27-webapps-minutes.html#action01]

<trackbot> Created ACTION-481 - Ask SVG and HTML WGs what their recommended approach is for getting the selected text (related to select event) [on Doug Schepers - due 2010-02-03].

<scribe> ACTION: Travis to draft flow diagram for interaction between focus(), blur() APIs and focus/blur events (including focusin/focusout) [recorded in http://www.w3.org/2010/01/27-webapps-minutes.html#action02]

<trackbot> Created ACTION-482 - Draft flow diagram for interaction between focus(), blur() APIs and focus/blur events (including focusin/focusout) [on Travis Leithead - due 2010-02-03].

wheel event and default actions

Resolution: Remove MouseWheel interface, and replace with a description of legacy events (DOMPixelScroll, mousewheel, etc.) in the wheel event's section

Travis: I concur

smaug: Yes, I agree too.

initEvents

<shepazu> http://dev.w3.org//2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-DocumentEvent-createEvent

smaug: I have a couple of issues with this.
... first the createEvent can now take event type names.

shepazu: Reason to change this was the proliferation of init*Events on every interface.

Reason I see to change this is for the use case of wanting a simple way to initialize only _some_ of the properties on a given event and leave the other properties as their defaults.

<smaug> http://www.w3.org/TR/cssom-view/#extensions-to-the-mouseevent-interface

When authors init events, there are just some properties that can't be initialized (because they're not in the init's param list)

I'd like you to add wording about what the default values are (generally) for an un-inited event.

Also, please revert back to the old init* APIs--I just don't think its time to take on that problem yet.

(In the future, I could see some kind of initParam("eventProperty", "eventPropertyValue")

)

I'd like to better understand the patterns that web developers are using here.

Spec Next Steps

shepazu: Assuming we get to CR, we're going to need a test suite and two interoperable implementations
... I'd love to see a script library available that allows these features to be used right away.
... I'll be looking for help with building tests
... In the next two weeks lets try to clean-up all remaining spec issues.

<shepazu> SENSE

<shepazu> Signalling Events and Notifications by Selector Expressions

<shepazu> Simple Eventless Notifications by Selector Expressions

<scribe> ACTION: shepazu to Email the list regarding reverting event initializers (to be tackled next version) and call for use cases. [recorded in http://www.w3.org/2010/01/27-webapps-minutes.html#action03]

<trackbot> Created ACTION-483 - Email the list regarding reverting event initializers (to be tackled next version) and call for use cases. [on Doug Schepers - due 2010-02-03].

shepazu: I think I could have most of the issues resovlved by next week. I will proceed with that goal.
... Let me know if there's anything outstanding.

<shepazu> trackbot, end telcon

Summary of Action Items

[NEW] ACTION: shepazu Ask SVG and HTML WGs what their recommended approach is for getting the selected text (related to select event) [recorded in http://www.w3.org/2010/01/27-webapps-minutes.html#action01]
[NEW] ACTION: shepazu to Email the list regarding reverting event initializers (to be tackled next version) and call for use cases. [recorded in http://www.w3.org/2010/01/27-webapps-minutes.html#action03]
[NEW] ACTION: Travis to draft flow diagram for interaction between focus(), blur() APIs and focus/blur events (including focusin/focusout) [recorded in http://www.w3.org/2010/01/27-webapps-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/01/27 20:32:06 $

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)

Found Scribe: Travis
Inferring ScribeNick: Travis
Found ScribeNick: Travis
Default Present: Shepazu, [Microsoft], Olli_Pettay
Present: Shepazu [Microsoft] Olli_Pettay

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

Found Date: 27 Jan 2010
Guessing minutes URL: http://www.w3.org/2010/01/27-webapps-minutes.html
People with action items: shepazu travis

[End of scribe.perl diagnostic output]