W3C

- DRAFT -

Web Applications Working Group Teleconference

07 Apr 2010

See also: IRC log

Attendees

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

Contents


<trackbot> Date: 07 April 2010

<smaug> https://bugzilla.mozilla.org/show_bug.cgi?id=556493

<smaug> Travis: https://bugzilla.mozilla.org/show_bug.cgi?id=556493

<scribe> Scribe: Travis

<scribe> ScribeNick: Travis

Click issue

smaug: if mousedown happens in different node then the mouseup event, then the click event does not fire.
... This is underspecified today.
... One of the nodes (the mousedown) is a textnode.

shepazu: From accessibility point-of-view, not firing click can be problemantic, especially if there is considerable mouse shaking/movement.

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

The bug reproduction is here: https://bug556493.bugzilla.mozilla.org/attachment.cgi?id=436452

shepazu: We can add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element"

Travis: IE8 and 9 do not manifest this bug.

<shepazu> ACTION: shepazu to add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" [recorded in http://www.w3.org/2010/04/07-webapps-minutes.html#action01]

<trackbot> Created ACTION-516 - Add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" [on Doug Schepers - due 2010-04-14].

shepazu: Everyone in agreement then?

smaug: Yes.

Travis: Yes.

i18n

<shepazu> http://lists.w3.org/Archives/Public/www-dom/2010JanMar/0051.html

Travis: I agree with the points 2-4 in full.

smaug: Yes, I also agree with those.
... What are the other comments?

Travis: Does this impact DocumentEvent:convertKeyValue?

shepazu: Not directly, but I was hoping for some review on this from i18n...
... convertKeyValue is generic; it takes any string (e.g, "U+571", "&#123", etc.) and converts to any of the four output key types.
... It has utility, but DOM Events may not be the right time/place for this API.
... Example, could provide "DEL" and it would spit out the delete character key (in unicode or some other format).

Travis: From a testing perspective, this might be hard to effectively test because of the large class of inputs/outputs.

shepazu: I think I will go ahead and drop this API from the spec.

Resolution: Drop convertKeyValue from DOM Events

DOM Views

<shepazu> http://www.w3.org/Bugs/Public/show_bug.cgi?id=9336

Travis: This seems to center around our UIEvent having a "view" property

<smaug> http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113/views.html

shepazu: Implementors implement the view as a Window.

<kenneth> smaug, there has been some talk about moving vm-i (view mode interface from Widgets 1.0) to CSSOM, so maybe the viewMode property should be moved to DOM-Level-2-Views?

<smaug> kenneth: move something to DOM-Level-2-Views?

<smaug> that is a very old spec

<kenneth> is there a newer spec for dom views?

<smaug> no

shepazu: In the glossary (section 2) the definition of defaultView seems very adaquate and addresses the concept of window as we read in the feedback.

<kenneth> smaug, ah there is the http://www.w3.org/TR/DOM-Level-3-Views/

<smaug> kenneth: I doubt anyone has worked on that Note for ages

<scribe> ACTION: smaug Ask for rationale on UIEvent "view" property feedback and send to www-dom and public-html [recorded in http://www.w3.org/2010/04/07-webapps-minutes.html#action02]

<trackbot> Created ACTION-517 - Ask for rationale on UIEvent "view" property feedback and send to www-dom and public-html [on Olli Pettay - due 2010-04-14].

<smaug> http://limi.net/articles/resource-packages

<shepazu> trackbot, end telcon

Summary of Action Items

[NEW] ACTION: shepazu to add an example to section 5.2.3.2 under the click event to clarify the sentence "The click event may be preceded by the mousedown and mouseup events on the same element" [recorded in http://www.w3.org/2010/04/07-webapps-minutes.html#action01]
[NEW] ACTION: smaug Ask for rationale on UIEvent "view" property feedback and send to www-dom and public-html [recorded in http://www.w3.org/2010/04/07-webapps-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/04/07 19:13:10 $

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, 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: 07 Apr 2010
Guessing minutes URL: http://www.w3.org/2010/04/07-webapps-minutes.html
People with action items: shepazu smaug

[End of scribe.perl diagnostic output]