<Travis> I will need to make this a short call, as I have to run somewhere in 20 minutes...

<Travis> http://status.modern.ie/

<masayuki> Travis: I see, no problem.

I updated chromestatus.com with info about Chrome's status

I also put in IE and FF info as far as I could.

code: http://www.chromestatus.com/features/5228092293382144

key: http://www.chromestatus.com/features/4748790720364544

For UIEvents, IE's status page has "Identify the physical key being pressed; Query key from layout.", which is the old content that I wrote for chromestatus and is no longer valid.

UIEvents no longer has |code|

For chromestatus, I update the UIEVent entry: http://www.chromestatus.com/features/5593215650496512

To cover just the locale and queryKeyCap stuff

<Travis> That's great. Thanks!

<masayuki> Firefox will rename KeyboardEvent.key value in 33 or 34 for comforming the latest spec. We're discussing the timing.

<masayuki> https://wiki.mozilla.org/RapidRelease/Calendar 33 will be released mid-October, 34 will be released late November

<Travis> Super!

Masayuki: is the best place to get FF status on MDN? Is there anything equivalent to chromestatus.com or status.modern.ie?

<Travis> I landed a change for bug 26019: https://dvcs.w3.org/hg/dom3events/rev/8034c1f1c711

<Travis> Would love your review.

<masayuki> garykac: When *I* work on the new feature, I update or create the MDN document. Therefore, I can yes for D3E feature.

I noticed that it was pretty accurate for |key| and |code|. Thank you for keeping it updated.

<masayuki> garykac: no problem. If you want to confirm the mapping with actual code, you can see...

<masayuki> key mapping: http://mxr.mozilla.org/mozilla-central/source/widget/shared/NativeKeyToDOMKeyName.h

<masayuki> code mapping: http://mxr.mozilla.org/mozilla-central/source/widget/shared/NativeKeyToDOMCodeName.h

<Travis> I need to take off now. Let's meet again on July 8th. (Two week break.)

So, we're skipping the next two weeks. Sounds good.

I don't have much this week.

<masayuki> Travis: Okay.

<Travis> See you all later!

<masayuki> See you.

But hopefully we can start talking about testing then.

<masayuki> garykac: could you check this? https://www.w3.org/Bugs/Public/show_bug.cgi?id=24739#c7

just a sec

<Travis> RRSAgent: please make the minutes

<masayuki> garykac: later is okay for reply of it.

If the Sun keyboard has two separate keys, then yes we should have two separate |code| values.

<masayuki> garykac: Yeah, it has.

So the Sun keyboard has separate "ContextMenu" and "Props" keys?

Where is the ContextMenu key located?

I'm looking at: http://iichan.hk/s/src/1355938735862.jpg

<masayuki> Wait a moment, I confirm it.

<masayuki> The "Compose" key is the "ContextMenu" key. Located below the "RightShift" and left of "AltGraph" key.

<masayuki> I confirmed on Japanese Sun keyboard, though.

OK. So that key is labelled "Compose" on all the Sun keyboard that I found (Keyboard Type 5, 6 & 7)

<masayuki> Yeah, my Sun keyboard is probably 7.

I think that key is probably better named "Compose" since it is Sun specific and the Sun keyboard doesn't have the same keys on the bottom row. I'll need to add images of the Sun keyboard.

<masayuki> Hmm, but we cannot distinguish whether the keyboard type is Sun or not.

Does "compose" use the same USB code as the Context Menu key?

<masayuki> The "Compose" key is just recycles the "ContextMenu"'s scancode :-(

OK.

<masayuki> garykac: yes.

Then ContextMenu is the best choice.

I'll add a note under ContextMenu that the the Sun "Compose" key should use this |code|.

<masayuki> I agree.

So, the bottom row of the Sun keyboard would be: CapsLock, AltLeft, OSLeft, Space, OSRight, ContextMenu, AltRight

sgtm. Thanks for catching that -- I'll have to dig up a Sun keyboard for testing.

<masayuki> Yes, the mapping is right.

Great.

Anyway, I have to run now. I'll talk to you in a few weeks.

<masayuki> Okay, see you.

I'll fix this bug in the next few days.

<masayuki> Thanks in advance!

<ArtB> Title: DOM 3 Events Call

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)

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

WARNING: No "Topic:" lines found.

Default Present: Travis, +1.425.936.aaaa, garykac
Present: Travis +1.425.936.aaaa garykac masayuki

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 18 Jun 2014
Guessing minutes URL: http://www.w3.org/2014/06/18-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