[i18n-activity] Why one code point only for accesskey values? (#720)

r12a has just created a new issue for https://github.com/w3c/i18n-activity:

== Why one code point only for accesskey values? ==
6.5.2 The accesskey attribute

> 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**.

Why is there a restriction on numbers of code points?  Wouldn't it be better to restrict to the value emitted by a single key press (plus any relevant modifier keys)?  Some keyboards have keys which produce more than one code point, eg.

1.  some Burmese vowels are composed of 2 or 3 codepoints, but are accessed by a single keypress on the Mac's Burmese keyboard (see https://r12a.github.io/pickers/burmese/?text=%E1%80%AD%E1%80%AF%20%E1%80%B1%E1%80%AC%20%E1%80%B1%E1%80%AC%E1%80%BA for a list)
2. the Mac Devanagari keyboard allows users to type sequences of 2 or 3 characters by pressing shift+key (see https://r12a.github.io/pickers/hindi/?text=%20%E0%A5%8D%E0%A4%B0%20%E0%A4%B0%E0%A5%8D%20%E0%A4%9C%E0%A5%8D%E0%A4%9E%20%E0%A4%A4%E0%A5%8D%E0%A4%B0%20%E0%A4%95%E0%A5%8D%E0%A4%B7%20%E0%A4%B6%E0%A5%8D%E0%A4%B0 for a list)

Testing on the Mac with https://w3c.github.io/i18n-tests/html/editing/assigning-keyboard-shortcuts/the-accesskey-attribute/exp_accesskey_000 reveals that Safari and Chrome recognise the multicode accesskey values.

**WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered.

**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:**

ยง link_to_issue_raised

Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/720 using your GitHub account

Received on Thursday, 25 July 2019 13:41:44 UTC