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.

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

Possible error: "Backspace" is listed in the Writing System Keys instead of Functional Keys table #34

Closed
Keavon opened this issue Aug 9, 2022 · 1 comment

Comments

@Keavon
Copy link

Keavon commented Aug 9, 2022

The table in section 3.1.1.1 Writing System Keys includes "Backspace" (it is the third entry). I believe this is an error.

Figure 13, the diagram for writing system keys, does not highlight Backspace:

Figure 13

It has 50 keys (51 including the duplicate Backslash) in green or blue. The (potentially) erroneous table has 51 entries (without the duplicate Backslash).

In the next section, 3.1.1.2 Functional Keys, the table is missing "Backspace" even though its figure 14 diagram does color in the Backspace key blue. Furthermore, the text above the diagram specifically calls out Backspace as an example of a functional key.

3.1.1.2. Functional Keys says:

The functional keys (not to be confused with the function keys described later) are those keys in the alphanumeric section that provide general editing functions that are common to all locales (like Shift, Tab, Enter and Backspace). With a few exceptions, these keys do not change meaning based on the current keyboard layout.
Figure 14
Figure 14 The standard set of functional keys in the alphanumeric section

This diagram has 14 keys in green or blue. But the table has only 13 entries. One extra entry in the Writing System Keys table and one fewer in the Functional Keys table.

Is Backspace a functional key or a writing system key? My conclusion is that the two tables erroneously list the "Backspace" entry in the wrong table.

@garykac
Copy link
Member

garykac commented May 9, 2023

Thank you for reporting this. It is fixed in the latest WD: https://w3c.github.io/uievents-code/

@garykac garykac closed this as completed May 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants