Design Review #238

#238: Keyboard Map

Visit on Github.

Opened Apr 6, 2018

今晩はTAG！

I'm requesting a TAG review of:

Name: Keyboard Map
Specification URL: https://wicg.github.io/keyboard-map/
Explainer, Requirements Doc, or Example code: Explainer
Tests: not available yet
Primary contacts: garykac

Further details (optional):

Relevant time constraints or deadlines: [please provide]
I have read and filled out the Self-Review Questionnare on Security and Privacy. The assessment is here.
I have reviewed the TAG's API Design Principles

You should also know that...

The problem this API is solving was pointed out as missing feature in a Mozilla Hacks post from last year (in the "What's missing?" section).

We'd prefer the TAG provide feedback as (please select one):

open issues in our Github repo for each point of feedback
open a single issue in our Github repo for the entire review
leave review feedback as a comment in this issue and @-notify [github usernames]

Discussions

Discussed Apr 1, 2018 (See Github)

Travis: I looked at this, added a few comments. I think our review is done. Sangwhan?

Sangwhan: They haven't fully responded yet; it would be good to hear their views.

Dan: Can we close it and ask them to come back at the next stage? Or do we need to keep it open and ask them to reply?

Sangwhan: I'd like us to get to a point of agreement, and then we can close our issue.

Travis: I agree.

Dan: How are we going to get that feedback? I'll ping Gary.

Travis: on their repo, issues 7, 8, 9, 14 and 15 are the ones we're looking at.

Comment by @torgo Apr 6, 2018 (See Github)

Discussed at Tokyo F2f.

Comment by @travisleithead Apr 6, 2018 (See Github)

Glanced through the explainer, which is very nice. Thanks!

Comment by @torgo Apr 7, 2018 (See Github)

Discussed at Tokyo f2f: https://cryptpad.w3ctag.org/code/#/1/view/TutVXt+MSZTzQmuNeMrHXg/exTf44AJ0kJSdxfe2TNzKjYoYFos1cbxppVwfGztRtM/

Comment by @cynthia Apr 7, 2018 (See Github)

@garykac, Thanks for bringing this up. We covered this during a breakout session in Tokyo, and have raised issues that were brought up on the spec side issue tracker as requested.

Comment by @torgo Apr 24, 2018 (See Github)

Waiting for feedback. @garykac can you let us know what the likely response to our feedback will be? Specifically your issues 7, 8, 9, 14 and 15? Thanks!

Comment by @garykac Apr 26, 2018 (See Github)

I've update the spec/explainer and added comments to those issues. Please let me know if you need additional info.

Comment by @cynthia May 4, 2018 (See Github)

@garykac Thanks a lot. Will take a look.

Comment by @plinss May 15, 2018 (See Github)

@garykac We'll be discussing this on https://meet.jit.si/w3ctag at 08:00 PDT on May 15, hopefully you can join us.

Comment by @torgo Nov 10, 2021 (See Github)

Just noting retroactively that we agreed to close this as satisfied in the May 15 2018 telecon.