Review TPAC.

Identify next high-prio items

A summary of items we discussed at TPAC:

Add 'Unidentified' to the |code| spec to be used when the code value cannot be determined (eg, with virtual keyboards)

Add descriptive text specifying how |code| should be set for virtual keyboards

Add images in spec for phone arrow pad and numpad section (show position of '*' and '#').

Remove the virtual modifier key 'Accel'

Remove the 'OS' key and have Windows return 'Meta' (similar to Mac)

Update section on mobile phone keys to specify that arrow keys and Enter should be used for the Android dpad keys.

Need to add example showing how composition events should fire when the composition string overflows the IME buffer.

Those are the big items that I have from TPAC.

<Travis> Have these issues been committed in the spec yet?

There were also various updates to the |key| values based on Android KEYCODEs.

I haven't written the updated descriptions nor have I created the new images.

But most of the |key| values have been updated.

I have a few more small updates (the "11" and "12" key, plus an updated desc for the "0" key for the HDMI-CEC usage)

<Travis> OK. Perhaps we should focus this week on landing those changes and then meet next week to review the next round? Also, I'd like to start a testing plan...

My assumption is that the work related to Ranges and contentEditable are being done by the Editing task force. And that we only need to track it to make sure it keeps moving forward.

The lack of progress with testing is my biggest disappointment with TPAC - the Editing meeting took over the time I wanted to spend on that. :-(

But we can do the testing on our own, whereas the Editing work needed the big group together...

travis: sgtm

I'll make my remaining changes over the next few days.

<Travis> That is my basic understanding as well. There was some discussion with the Editing TF about where to spec some of their changes, and I can't recall if we landed on a resolution.

<Travis> e.g., should the input and beforeInput algorithms be incorporated into our doc or kept in theirs...

<masayuki> SGTM, input and beforeinput are important for the relation between keyboard events and composition events. The document which recommend web developers to use them instead of key events should be in UIEvents spec.

As for where this should live, the Edit TF will keep |beforeinput| and |input| for now, but we need to keep the info about the order of events (relative to other events) in UIEvents.

So, the info will be split (unfortunately) between Editing and UIEvents.

Longer term, I think it makes sense to move the InputEvent IDL into UIEvents.

But it makes sense for it to stay in Editing for the time being as long as they are actively working on it and making progress.

To clarify: the info will be split because all of the Editing info related to these events belongs in the Editing spec, not in UIEvents. Whereas UIEvents needs to have the event-order info.

masayuki: There was one |key| value that changed name: 'MediaSkip' -> 'MediaSkipForward'

Because we now have 'MediaSkipBackward'

<masayuki> garykac: Oh, thank you for the information.

That's all I have for this week.

I'll be landing the updates we agreed up over the next week.

<masayuki> I think that Firefox will follow the new key spec at Firefox 45 or 46.

masayuki: I should have all those Android key codes that you requested added to the spec in the next week.

<masayuki> garykac: Thank you for your great work!!

No problem. I love the progress that Mozilla is making in this area.

For next week, I think we should split time 50/50 between going over the bugs and working on a test plan.

Probably start with bugs and then switch over to testing...

<Travis> Sounds good to me.

I just fixed https://github.com/w3c/DOM-Level-3-Events-code/issues/6 (removing USB Usage IDs from the |code| tables.

By next week, my plan is to close out all the |key| and |code| bugs.

Anyway, I'm going to head out. now.

Same time next week?

<Travis> Same time.

<Travis> Thanks Gary.

<masayuki> Okay, see you next week.

See you all then.

Thanks

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: garykac joannawu marcosc masayuki tantek 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: 04 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/04-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