See also: IRC log
RRSAgent: this meeting spans midnight
<garykac> hello?
<masayuki> Hello.
<garykac> Did you see this posting to public-webapps: http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0519.html
<garykac> Regarding the term "default action"
<garykac> We use "default action" through the D3E spec - but it seems like we should use a different term to avoid confusion
<garykac> It seems like we should also call out onclick (and the other two? events) that are inconsistent with the rest of the events
<garykac> See also the discussion at the end of https://www.w3.org/Bugs/Public/show_bug.cgi?id=12230#c25
What are some of the bugs we'd like to have addressed before last call?
(Ideally all bugs, but this is not a requirement)
The bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=25485 is probably one to address (integration with DOM4)
Gary is cooking up a change to https://www.w3.org/Bugs/Public/show_bug.cgi?id=25723 at the moment as well...
<masayuki> I want to resolve this https://www.w3.org/Bugs/Public/show_bug.cgi?id=25683
<masayuki> even if it's not defined, D3E should define browsers MAY delay to fire some events and they become non-cancelable events.
Makes sense.
Let's now review the email we wanted to send last week: https://docs.google.com/document/d/1VqwfHyNDtoOoDzZZ7xZlrcxtcy8ZORV1pUoRjRbwJro/edit?pli=1
The feedback we got was that some of the prose here is very useful for a conceptual understanding of the algorithms in DOM4.
We could consider leaving in (after cleaning up) section 3, while removing only section 4 (the basic event interfaces)
Section 4 has an intro graphic which was helpful showing the event's hierarchy
But then, 4.1, 4.2, 4.3, 4.4 are all redundant.
4.5 also (I noticed that IE adds createEvent to SVGSvgElement
scribe: but no other browser does this)
<masayuki> IE supports event constructor, why is it added to SVGSvgElement? I think that this should be legacy and browsers shouldn't add support range if there are no resonable reasons.
<masayuki> E.g., for improving compatibility with other browsers.
(garykac is fixing Fig. 2 right now.)
Proposal for https://www.w3.org/Bugs/Public/show_bug.cgi?id=25485 is to...
Remove the formal IDL definitions of sections 4.1, .2, .3, .4, and .5
2) Move the hierarchy diagram into section 3
3) Run an editorial pass over section 3 to make it officially non-normative
(remove the MUST and MAY text in favor of "can" and "might", etc.)
(easy reading explainer)
We may want a non-normative replacement for the API definitions of DOM4, so that we can cross-link within our document without requiring the reader to leave the spec entirely for the definitions.
(Sorry: the IDL definitions currently in section 4)
<garykac> It sounds like we no longer need to send the email out.
<garykac> Since we're going to keep the sections, and only remove the redundant stuff.
Let's see if we can tackle some remaining bugs, and then the editors will attempt this next monday.
Does anyone have a conflict with another DOM 3 Events telecon next week?
<masayuki> no problem
<garykac> See everyone next week - we're hoping (once again) to have most of the bugs resolved by then.
<garykac> I'll finish up figure 2 (and update the spec to remove the "issue")
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: Travis Inferring Scribes: Travis Present: Travis garykac masayuki WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 21 May 2014 Guessing minutes URL: http://www.w3.org/2014/05/21-webapps-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]