- From: Doug Schepers <schepers@w3.org>
- Date: Fri, 23 Apr 2010 10:27:51 -0400
- To: "www-dom@w3.org" <www-dom@w3.org>
http://www.w3.org/2010/04/21-webapps-minutes.html
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Web Applications Working Group Teleconference
21 Apr 2010
[2]Agenda
[2] http://lists.w3.org/Archives/Public/www-dom/2010AprJun/0031.html
See also: [3]IRC log
[3] http://www.w3.org/2010/04/21-webapps-irc
Attendees
Present
Shepazu, [Microsoft], Olli_Pettay
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Travis
Contents
* [4]Topics
1. [5]Issues review
2. [6]set/releaseCapture.
3. [7]magnify reference misleading?
4. [8]trusted/untrusted events?
5. [9]FocusEvent relatedTarget
6. [10]Focus event types interaction (Issue 102)
7. [11]wheel event, button value
8. [12]dead key values during composition
9. [13]JavaScript escaped characters
* [14]Summary of Action Items
_________________________________________________________
<trackbot> Date: 21 April 2010
<smaug> just a minute
<scribe> scribe: Travis
<scribe> scribeNick: Travis
Issues review
Current editor's draft dated 4/20/2010:
[15]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event
s.html
[15]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html
shepazu: Many issues resolved in this draft.
... after review, we will be ready to publish (Working Draft)
... would like to go to LCWD in first two weeks of May.
smaug: I see setCapture still. Looks to have issues...
<shepazu>
[16]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event
s.html#events-event-type-setCapture
[16]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-event-type-setCapture
set/releaseCapture.
smaug: Recommend not taking these for D3E -- many unresolved
issues...
shepazu: [discusses possible use cases]
I am also in favor of postponing this to a future spec.
scribe: many of the use-cases can be handled via the capture phase
of the event model. Granted, capturing events over an iframe is not
possible, however, we have had known security exploits as a result
of this feature in IE.
magnify reference misleading?
We all resolve to remove it because it might lead folks to think
that it's spec'd somewhere...
shepazu: OK. removed.
trusted/untrusted events?
shepazu: I think we've already resolved this...
FocusEvent relatedTarget
Speced as the eventTarget recieveing focus...
<shepazu>
[17]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event
s.html#event-type-focus
[17]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-focus
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"[18]http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
[18] http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
<html xmlns="[19]http://www.w3.org/1999/xhtml">
[19] http://www.w3.org/1999/xhtml
<head>
<title> Untitled Page</title>
</head>
<body>
<form>
<input id="myCheck" name="checky" type="checkbox" />
</form>
<script>
var check = document.getElementById("myCheck");
check.addEventListener('click', function(e)
{
alert('preventing the default action');
e.preventDefault();
}, false);
</script>
</body>
</html>
(That's a sample code that "undoes" the check action after the fact,
via preventDefault.)
(This is related to the issue in default actions.)
shepazu: Great. I'll clean this up and keep the wording as-is.
Back to relatedTarget/focus event type...
IE9 is currently reporting the same object for relatedTarget as
target. We can adjust this if necessary...
smaug: Yes, I don't see why we need to have them both point to the
same place...
shepazu: OK. I'm changing relatedTarget to be 'null' in cases where
the relatedTarget and target are the same in the FocusEvent
interface.
Focus event types interaction (Issue 102)
<scribe> ACTION: shepazu to coordinate with WAI with issues of
focus. [recorded in
[20]http://www.w3.org/2010/04/21-webapps-minutes.html#action01]
<trackbot> Created ACTION-529 - Coordinate with WAI with issues of
focus. [on Doug Schepers - due 2010-04-28].
<shepazu>
[21]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event
s.html#event-type-wheel
[21]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-wheel
(back to focus/blur topic... I sent the mail re: this topic on Feb
8, 2010, but it may have been rejected from www-dom. I just resent
it to www-archive.
wheel event, button value
Firefox: it appears to be 0 (which is the default when no value is
assigned)
Opera: seems kinda random 0's, 1's, and 2's reported...
shepazu: Should there be an associated button?
I like just having button and 'buttons' be zero.
smaug: me too.
shepazu: OK. Done.
<shepazu>
[22]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event
s.html#keyset-DeadKeys
[22]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#keyset-DeadKeys
dead key values during composition
<shepazu>
[23]http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Event
s.html#key-values
[23]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#key-values
shepazu: Simple resolves...
JavaScript escaped characters
All the issues listed seem more like a Note than an issue.
shepazu: Agree.
Might even get its own section, a la "Considerations for key values
in other language bindings"?
shepazu: Do we need to worry about C/Java interactions?
... the implementation will just need to handle it.
... I'm going to convert these to notes.
... I think that's the last major issue!
smaug: When the draft is updated, and before publication, please
send out a mail.
<shepazu> trackbot, end telcon
Summary of Action Items
[NEW] ACTION: shepazu to coordinate with WAI with issues of focus.
[recorded in
[24]http://www.w3.org/2010/04/21-webapps-minutes.html#action01]
[End of minutes]
Received on Friday, 23 April 2010 14:27:55 UTC