Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Why reduce accesskey values to a single code point? #482

Closed
r12a opened this issue Sep 15, 2017 · 3 comments
Closed

Why reduce accesskey values to a single code point? #482

r12a opened this issue Sep 15, 2017 · 3 comments
Labels
close? The related issue was closed by the Group but open here needs-resolution i18n expects this item to be resolved to their satisfaction. s:html https://html.spec.whatwg.org/multipage/ t:loc_input_x 9.6 User input (TBD) wg:webplatform https://www.w3.org/groups/wg/webplatform

Comments

@r12a
Copy link
Contributor

r12a commented Sep 15, 2017 •
edited
Loading

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ w3c/html#1022
@r12a r12a added s:html https://html.spec.whatwg.org/multipage/ pending Issue not yet sent to WG, or raised by tracker tool & needing labels. and removed pending Issue not yet sent to WG, or raised by tracker tool & needing labels. labels Sep 15, 2017
@r12a r12a added the needs-resolution i18n expects this item to be resolved to their satisfaction. label Nov 16, 2018
@himorin
Copy link
Contributor

himorin commented Jul 2, 2019

6.5.2 The accesskey attribute
says

If specified, the value must be an ordered set of unique space-separated tokens that are case-sensitive, each of which must be exactly one code point in length.

This state does not require any procedure to reduce accesskey values, but may remain in conflict with i18n-tests https://www.w3.org/International/tests/repo/results/accesskey#multiple ?

@r12a
Copy link
Contributor Author

r12a commented Jul 11, 2019

I propose we close this tracker (issue already closed) and refer instead to issues being prepared for the WhatWG spec.

@r12a r12a added the close? The related issue was closed by the Group but open here label Jul 11, 2019
@r12a
Copy link
Contributor Author

r12a commented Jul 11, 2019

Agreed to close during telecon.

@r12a r12a closed this as completed Jul 11, 2019
@r12a r12a added the t:loc_input_x 9.6 User input (TBD) label Aug 10, 2022
@w3cbot w3cbot added the wg:webplatform https://www.w3.org/groups/wg/webplatform label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
close? The related issue was closed by the Group but open here needs-resolution i18n expects this item to be resolved to their satisfaction. s:html https://html.spec.whatwg.org/multipage/ t:loc_input_x 9.6 User input (TBD) wg:webplatform https://www.w3.org/groups/wg/webplatform
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@himorin @r12a @w3cbot