<Travis> Hi!

<masayuki> Travis: hi!

<masayuki> garykac: hi.

hello

<Travis> Agenda:

I updated the github uievents readme with the updated info for this meeting.

<Travis> Review recent activity

<Travis> I was able to transfer over our meeting minutes to Github.

<Travis> https://github.com/w3c/uievents/wiki/Meeting-Notes

<Travis> Now, there is nothing in the old WebApps wiki.

<Travis> (And I put a link to the new home in case anyone stumbles there by accident.)

I fixed most of the |key| and |code| bugs

There are no outstanding |key| bugs.

<Travis> Very nice!

There are 3 remaining |code| issues:

<masayuki> Thank you, to implement them on Firefox is in my queue.

featurephone section (which require text and a figure -- all the |key| values have been defined)

<Travis> https://github.com/w3c/DOM-Level-3-Events-code/issues

Unidentified: needs text added to the spec describing when it should be used.

it's related to the last issue:

Need text to describe what to do with |code| for virtual keyboards and other non-standard cases.

Other than |Unidentified|, all of the |code| values are in the spec.

<Travis> Excellent progress.

<Travis> I noticed in Issue 47: https://github.com/w3c/uievents/issues/47 -- we are no longer blocked!

I didn't look at any of the UIEvents bugs - I just focused on key and code bugs.

<Travis> I had intended to put some of the "quick fix" bugs to rest, but got off track.

<Travis> Now looking at issue 50: https://github.com/w3c/uievents/issues/50

<Travis> Some good text from HTML5: http://www.w3.org/TR/html5/obsolete.html#obsolete

Propose changing: "This section is informative" -> "This section is normative, but these features are deprecated. They should only be implemented by user agents that require compatibility with legacy software."

deprecated or obsolete? any preference?

<Travis> I'd break it into two sentences: This section is normative. The following features are obsolete and should only be...

<Travis> Issue 43 - https://github.com/w3c/uievents/issues/43

I resolved that bug (Legacy appendices)

The "file a bug" link still goes to bugzilla :-(

<Travis> Here's a way to do it: https://github.com/w3c/media-source/issues/new

That opens the new bug page, but it doesn't copy the text into the bug.

I'm not sure how to do that with github (other than via a POST, which is more effort than it's worth)

<Travis> Maybe we can drop the feature. I'm not sure how helpful it has been...

<Travis> (Gary fixes a couple of easy bugs.)

The bug link should now go to github rather than bugzilla

<Travis> Let's talk about testing...

We should definitely do it.

https://github.com/w3c/uievents/issues/25 seems like a meta bug covering all of our testing.

<Travis> We would like to have tests that cover all of our event order descriptions (at a minimum)

And I would like to get some manual tests to verify our |key| and |code| values for different keyboard/locale combos.

<Travis> We'd like to rename to ui-events-key and ui-events-code

Yes, the rename would be nice if it's possible

We should try to clean up the references to DOM3 in the spec.

OK. We got a few more issues resolved.

<Travis> We'll try to meet again next week, but I won't be available the following week. (The 24th.)

OK.

<masayuki> no problem.

Next week we can perhaps talk more about testing.

sounds good.

'til next week...

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: Travis Unidentified garykac https marcosc marcosc_ masayuki paul___irish tantek zcorpan
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: 11 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/11-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