<masayuki> Travis: hi

<Travis> hi!

<Travis> Great to see you will be going to TPAC.

<masayuki> me too.

<Travis> Gary's been active in moving bugs to Github issues.

<Travis> Gary's joined.

<masayuki> Yeah, I received a lot of bug spam ;-)

<masayuki> garykac: hi

hallo everyone

So, I'll be in Sapporo from (late) Sat night until Thu afternoon. Then I'll be in Tokyo until Sat.

I'm guessing that we'll do most of our discussions Mon-Wed.

<masayuki> I'll be there from Sunday night to Wednesday morning.

<Travis> garykac: https://dev.modern.ie/platform/status/

<masayuki> garykac: I'll research all .key and .code values of Chromium soon. If I find some difference between Chromium and the others, how should I do? Filing new issue per key?

masayuki: It depends on the type of difference. Hopefully, the diffs are only minor and we can file per-key. But if there are a bunch of related diffs, then having a single issue that tracks them all is easier.

travis: Chromium equivalent: https://www.chromestatus.com/features

<masayuki> garykac: I see.

code is: https://www.chromestatus.com/features/5228092293382144

key is: https://www.chromestatus.com/features/4748790720364544

One issue that came us was that we didn't spec an 'Unspecified' value for 'code', so we can't tell the difference between 'not implemented' and 'implemented, but unable to determine code'.

This can be an issue for virtual keyboards.

We have 'Unspecified' for 'key', but we didn't do the same for 'code'.

I'm opening a bug for this, but wanted to run it past everyone.

<Travis> Seems fair enough to add it--though it's usually just a flag to add the value into the spec or document it somehow.

Issue: https://github.com/w3c/uievents/issues/20

<trackbot> Created ISSUE-187 - Https://github.com/w3c/uievents/issues/20. Please complete additional details at <http://www.w3.org/2008/webapps/track/issues/187/edit>.

Issue:

uh oh

I've confused trackbot...

I also wanted to talk about our testing plan

<Travis> OK. Testing plan!

<Travis> More immediately... how to use our time at TPAC?

My plan for Japan is to:

(1) get the easy stuff out of the way *before* TPAC

(2) focus on the tricky issues that require discussion and iteration

I assume that we'll talk a bit about testing as well, but I want to make sure that we touch each bug so that we identify the problem/difficult cases that we want to focus on in person.

Step 1 is moving them into the github tracker. Although that's on hold until I can train the auto-mailer to stop spamming the mailing lists.

Step 2 is to clear out the low-hanging fruit (easy to fix or resolve)

Step 3 is TPAC!

Step 3 will be long...

But it should get us unblocked on the complex issues that are hard to deal with over the teleconf.

What does everyone else want to accomplish at (or before) TPAC?

Note we're currently at 48 issues (split between Bugzilla and github)

I'd like to get that down below 20 before the end of the quarter.

<Travis> There are some event definitions which we think are actually being defined more precisely in other specs (e.g., 'scroll', 'resize', etc.) should we try to clean these out of the spec before TPAC?

Good point.

It would be nice to at least identify them so that we can talk to the appropriate people who manage the other spec.

It'd be nice to know what they're thinking before we remove it.

I'd love to remove it, but IIRC there were cases where we had additional info in our spec that wasn't present in the other specs.

<masayuki> I'm confused about input/beforeinput event which were separated to another spec, but they are renamed to edit/beforedit. So, there is no spec to define input...

I didn't realize that they renamed it.

<sigh>

<masayuki> https://w3c.github.io/editing/input-events.html

<Travis> Folks in the Editing TF are indeed looking into it.

<Travis> I'm actually pretty happy they took it, as it is a major point of instability in our spec...

If they did, then we need to update a bunch of stuff in our spec.

We need to track their changes to make sure everything still works the way we expect it to.

<Travis> Yep. Pretty sure they took it--and yes, we need to clean up our doc. https://github.com/w3c/uievents/issues/2

We'll probably think about another spec release after we incorporate the changes from TPAC.

WRT testing...

I wanted to create a test suite that we can iterate on in the UIEvents repo

This will allow us to play around a bit more with it before we integrate with the official W3C test repo

Once we have a better set of tests, then we can send a pull request to the W3C repo to add them to their proper home.

Since there will be some test-related meetings at TPAC, I want to get a couple more tests "done" so that we can have better discussions with the other test folks (like TestDriver stuff)

<Travis> So... we can do that, but we can also just create a branch in our own forks for w-p-t, and play in the same way (with the rest of the infrastructure intact)

OK.

I put myself down as an Observer for the testing sessions. I'm hoping to talk with folks about testing integration.

<Travis> Awesome.

We have calls scheduled for Oct 13 and Oct 20.

The week after that is TPAC.

<Travis> So, for next week, Gary, you can have the issues moved out of bugzilla and into github?

We should meet briefly the next two weeks to: (1) clear out the easy stuff, and (2) build a list of things to talk about at TPAC

<Travis> We can have a working meeting next week to identify easy-to-fix issues and make assignments...

travis: yep, although I need to coordinate with Mike about the email spam.

That's the only blocking issue.

<masayuki> # I need to go out soon, so, I'm away from keyboard for preparation. Sorry.

masayuki: OK, talk to you next week.

<Travis> See you next week.

OK. see you all next week.

<Travis> RRSAgent: generate the minutes

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)

No ScribeNick specified.  Guessing ScribeNick: garykac
Inferring Scribes: garykac

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: Issue garykac https jungkees marcosc masayuki sicking trackbot travis
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


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: 07 Oct 2015
Guessing minutes URL: http://www.w3.org/2015/10/07-webapps-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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