[i18n-activity] Why reduce accesskey values to a single code point?

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

== Why reduce accesskey values to a single code point? ==
5.5.2. The accesskey attribute

> The user agent may strip content from value to reduce the length of value to a single unicode code point. 

Why is this done? What benefit does it bring?  Note that Chrome and Safari are capable of matching an accesskey attribute against a keypress that produces more than one character (see https://www.w3.org/International/tests/repo/results/accesskey#multiple).

This also seems to contradict earlier text:

> Printable characters that may represent more than one Unicode code point, such as accesskey="श्र", are valid 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:**


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

Received on Friday, 15 September 2017 12:16:11 UTC