UI Events teleconference

<masayuki> Travis: Hello.

Hi! Welcome. Glad you got the right time.

Calling in?

Agenda building time?

a+ Time to talk about the bug

<garykac> We're in a new repo now

<garykac> which means that I have to set that up...

<garykac> :-(

https://www.w3.org/Bugs/Public/buglist.cgi?component=UI%20Events&product=WebAppsWG&resolution=---

The spec is now here: https://w3c.github.io/uievents/

Repo is here: https://github.com/w3c/uievents

Two issues: https://github.com/w3c/uievents/issues

scribe: (looking things over)

Are there any high-priority bugs to address first?

scribe: e.g., can we prioritize our list?

<masayuki> In my work, https://www.w3.org/Bugs/Public/show_bug.cgi?id=21120 and https://www.w3.org/Bugs/Public/show_bug.cgi?id=26218 are important.

<masayuki> But it's okay not today because I work on others right now.

masayuki: super.

<masayuki> I hope that you guys check them when you have much time ;-)

<garykac> Did either of you see the InputDevice API "sketch" proposal that was sent out? https://lists.w3.org/Archives/Public/www-dom/2015JanMar/0102.html

<garykac> This is relevant to some discussions that we've had regarding the keyboard layout and current locale.

<garykac> If that proposal gains traction, it seems like the most appropriate place for that sort of info.

I didn't.

scribe: In looking at this, seems interesting.

<garykac> masayuki: we're trying to get back into it... it's been a while...

I'm thinking of asking us to do something crazy...

scribe: how about we stop focusing on editing the spec...
... and instead start focusing on writing the tests that we'll need.

<garykac> I agree.

<garykac> The parts in the spec that we need to work on fall into two main categories:

scribe: It will help us inform the final content of the spec anyway...

<garykac> (1) easy bugs (like assigning a name to a special key)

<garykac> (2) re-write bugs - as in please specify the interactions in more detail

<garykac> #2 will require that we write tests as we document the current interactions.

<garykac> Anything that we document will prompt the question: do the current browsers agree with the description. To answer this, we'll need these tests.

Those interactions have changed a little in Microsoft's new browser. Hopefully in favor of stronger interop.

<garykac> My confusion with the tests in the past is that:

<garykac> (1) they seemed to exist in multiple places (and I didn't know which ones were the most recent/most valid)

<garykac> (2) I wasn't sure what the best format was for the tests so that they would be most useful to all the browser vendors

I think we are the owners/gatekeepers of the tests (at least insofar as they apply to our spec), so we should dive in to see what we want to keep, what to toss out, etc.

<garykac> I recall that someone was spearheading a big test push in w3c, but I don't recall the details

<garykac> ... I just looked it up, it was Tobie back in 2013: http://www.w3.org/blog/2013/02/testing-the-open-web-platform/

<garykac> I don't know what came out of that or what was decided

<garykac> If there are current W3C best-practices, we need to know what they are

The resource I use is http://testthewebforward.org/

That site has the best-practices, etc.

move to agendum 2

The mirror of the test suite is: http://w3c-test.org/

garykac: wondering if we can sit-down and run through this?

http://w3c-test.org/dom/events/Event-constants.html

Re: agenda 2, I'm not sure we will have any problems working in Github, just need to start.

Do we have a preference for working in Github (e.g., using their issue-tracker), or keeping in Bugzilla, or both?

<garykac> Does the github tracker have good integration and tracking?

I think since the bulk of our bugs are in bugzilla, it makes sense to keep that as our primary source.

<garykac> I don't have strong feelings. It's nice to have it all in one location. But it's not unreasonable to have the tests tracked separately.

(Potentially transferring issues into bugzilla to keep it all consistent.

<garykac> I don't mind experimenting. We can always move the issues later if needed.

?

garykac: Which browsers should be our reference browsers?

Blink, Edge, Gecko, WebKit

<garykac> Blink has diverged from Webkit in many ways, but I'm not sure if that impacts things like the events ordering

move to the next agendum

<garykac> If they are too similar, then it doesn't make sense to count them as two "votes" for the common behavior. We'll have to investigate a bit and see.

If we're going to be focusing on testing, I'm not sure when our next milestone will be.

What should we plan for our next milestone?

garykac: My sense is we have small and large bugs.
... for the spec, we should write the sections that more accurately describe how events are fired (order and interactions)
... updating the format, language, etc.
... that is the next big milestone to shoot for.
... lots of small things in between.
... I think the deviceinfo thing is a distraction for right now.
... rewriting the sections and have the data to support them.

Should we look holistically or consider event sequences in isolation?

garykac: I hope some relatively small subset exists.
... once we have a small sample out there, people can judge and provide feedback.
... if we know now what subset we should do, we could focus on that (I'm not sure what that would be)

We could try starting with Focus events?

Perhaps we could try starting with the user actions/scenarios.

?

garykac: Perhaps focus is a good place to start.

What is our plan for the next call?

garykac: I'm going to be gone from mid-July to mid-August.

I'm going to be gone for large parts of July and august also.

<masayuki> I'm not available the last weeks of June and July.

Proposal: we should meet in two weeks.

Gary and I can schedule some time out-of-band to look at testing and understand how to write it up.

Next meeting on the 23rd.

<garykac> masayuki: Are you still around on the 23rd?

<masayuki> No, I cannot join the last week of this month...

<garykac> oh, the 30th is the last week. We thought that you would be around the 23rd.

masayuki: Can you make the 30th?

<masayuki> Ah, sure. I meant its previous week.

<garykac> If you can't be around the 23rd or the 30th, then maybe we should just go ahead with meeting on the 30th since that'll give more time to work on the testing items.

<masayuki> Yes, 30th is Okay.

Ok, to be clear, are you available for the 23rd or the 30th?

got it.

<garykac> well, then. the 30th seems to work then.

<garykac> ok.

<garykac> until the 30th...

That's it for now. See you all on the 30th. Gary, I'll see you sooner!

<masayuki> See you, thank you.

<garykac> bye

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/more/move/
Succeeded: s/unitl/until/
No ScribeNick specified.  Guessing ScribeNick: Travis
Inferring Scribes: Travis
Default Present: Travis, +1.425.936.aaaa, garykac
Present: Travis +1.425.936.aaaa garykac Travis_Leithead 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: 10 Jun 2015
Guessing minutes URL: http://www.w3.org/2015/06/10-webapps-minutes.html
People with action items: