search

w3c / i18n-request

Horizontal review requests are made via issues in this repo, and tracked by our radar.
https://github.com/orgs/w3c/projects/91/views/1
1 stars 7 forks source link

UI Events Keyboard Events Key Values 2022-11-29 > 2023-01-31 #199

Open LJWatson opened 1 year ago

LJWatson commented 1 year ago

Name of your specification

UI Events Keyboard Events Key Values

URL of your specification

https://w3c.github.io/uievents-key/

When does the review need to be finished?

2023-01-31

What has changed since any previous review?

A self-review was carried out and the Editor found that none of the criteria applied. This is recorded on the specification repo. There is however a note left in redsponse to the a11y self-review that may be of interest, recorded earlier in the same issue:

A note related to the FAST checklist item: "If technology provides internationalization support". This specification inherently defines {{KeyboardEvent/key}} values that support international hardware, e.g., keyboards for different languages or layouts. It also defines many special keys which are given human-readable names (like "Shift", "Control", "Home" or "ArrowLeft"). These special key values are defined as human-readable strings so that code to detect special keys can be easier to understand. While these values are not intended to be exposed directly to users, there is nothing preventing that. Apps that choose to expose these values would need to determine whether or not it is appropriate to translate these strings for presentation (e.g.: presenting "Backspace" as "Suppr. arrière" for French users).

We are hoping to transition to CR in February.

Please point to the results of your own self-review

No response

Where and how should the i18n WG raise issues?

No response

Pointer to any explainer for the spec

No response

Other comments

No response

LJWatson commented 1 year ago

@xfq do you know when your review might be completed? With thanks.

aphillips commented 1 year ago

@LJWatson I18N completed a review on 9 December and there are two open issues as a result. These are: w3c/uievents-key#58 and w3c/uievents-key#59. Neither seems to have been addressed in your current spec.

In the course of checking on this, I happened to notice that this spec also has a minor problem with Unicode character references. I filed a bug in our repo (as w3c/i18n-activity#1652) which will likely be forwarded to you next week.

By the way, you can check the status of your issues in the review tracker tool. Also note that this issue shows history on our Review Radar--in this case that the request was moved to "Awaiting Comment Resolution" on 9 December. That state is a completed review with open issues (vs. "Completed", which is when all our issues are closed)

LJWatson commented 1 year ago

Thanks @aphillips and apologies for the unnecessary chase. My fault entirely for looking in the wrong places for information.