See also: IRC log
RRSAgent: this meeting spans midnight
<masayuki> Hi.
<garykac> Hello
Hi!
I've had some recent conversations with HTML5 co-chairs about their references to our spec.
There is a concern that we may not be to Rec by the time that HTML5.0 goes to REC (anticipated by EOY).
<garykac> Were there any places in particular that they were concerned about?
I don't recall any specific references, only that there was "a dependency" there.
I've looked through the spec recently to find the places where DOMEVENTS is referenced.
These seem to included references to "click", other mouse events, mutation events, and focus events.
Notably, I did not see any references to our spec from the input/beforeinput
http://www.w3.org/html/wg/drafts/html/master/single-page.html
(That's 5.1)
Latest 5.0 heartbeat:
http://www.w3.org/TR/2014/CR-html5-20140204/
beforeinput does not seem to be there.
'input' is referenced. I searched for "named input" to find the occurances.
'input' seems to be fully specified in the spec (it's a "simple event" of Event interface).
Here is where beforeinput may have been used:
https://dvcs.w3.org/hg/editing/raw-file/tip/editing.html
<garykac> AFAIK, no one is working on that at the moment.
That spec makes "beforeinput" (for editing and use in execCommand) a EditingBeforeInputEvent
Editing spec appears to have stalled a bit.
<garykac> On 20 Feb 2013, Aryeh posted to public-webapps confirming that he is no longer actively working on it, but would be happy to help a new editor get up to speed.
<garykac> So I don't expect anything to come out of that spec anytime soon.
Back to testing... In terms of unblocking the HTML5 spec, we may want to concentrate our efforts on testing the parts of our spec that are referenced from HTML5.
Happily, the Keyboard events are not called out, so that may give us some lead time.
We could prioritize testing the parts of the spec that HTML5 depends on (the older stable stuff), so that if anyone comes asking us, we can say that the parts that HTML5 depends on are solid and have the proof of that in hand.
<garykac> What exactly do you mean by "testing" these parts? You mean independent vendor testing or official W3C tests?
Well, there are multiple definitions... :)
<garykac> What are people looking for? These events are fairly hard to test in an automated way.
I think the conformance folks will want to see tests that can be used in an implementation report.
So, automated or not, it doesn't really matter.
<garykac> Would they be content with manual tests?
<garykac> Sounds like it
Yeah.
<garykac> We'll have to dig into the tests and figure out where we stand...
While you are focused on editing the spec, I can review what tests exist for DOM3 in web-platform-tests, and whether the "basics" are already covered...
<garykac> BTW, do we (should we) provide a link to the tests in the spec?
<garykac> It seems like it would be useful, but I haven't seen other specs do that.
I noticed that reSpec has a convenient hook for reporting the test suite location...
<garykac> One global test location? Or a pointer from each relevant section in the spec?
A URL to a test suite (any path)
It goes in header section.
Example: https://dvcs.w3.org/hg/innerhtml/raw-file/tip/LCWD-DOM-Parsing-20131205.html
garykac: We should collate all the tests we can find and point them out.
<garykac> sounds good. I'd love to add these links in the spec.
garykac: AnneVK had some feedback
on UI Events.
... he may be hoping that UI Events details this.
... doesn't seem to affect DOM3.
(Bug list)
For next week !
16 bugs
We can review them next week.
That's all I've got for today!
<garykac> We'll meet again next week and I'll have some updates on the bugs.
Sounds good.
<garykac> Talk to you all next week.
RRSAgent: make logs public
RRSAgent: generate the minutes
<scribe> scribe: Travis
<scribe> scribeNick: Travis
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) Found Scribe: Travis Inferring ScribeNick: Travis Found ScribeNick: Travis WARNING: No "Topic:" lines found. Default Present: [Microsoft], +1.425.936.aaaa, garykac Present: [Microsoft] +1.425.936.aaaa garykac Travis 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: 05 Feb 2014 Guessing minutes URL: http://www.w3.org/2014/02/05-webapps-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]