W3C home > Mailing lists > Public > www-international@w3.org > October to December 2016

[uievents] Issue: 'Key value' terminology is ambiguous and confusing marked as i18n-comment

From: r12a via GitHub <sysbot+gh@w3.org>
Date: Fri, 16 Dec 2016 14:04:35 +0000
To: www-international@w3.org
Message-ID: <issues.labeled-196066426-None-sysbot+gh@w3.org>
r12a has just labeled an issue for https://github.com/w3c/uievents as 

== 'Key value' terminology is ambiguous and confusing ==
2. Keyboard Event key Value Tables

I found it very hard to get to grips with the text about keyboard 
events in the three specs uievents, uievents-key and uievents-code 
because it seemed that the two words 'key' and 'value' were juxtaposed
 to mean more than one possible thing.

One suggestion would be to refer to the KeyboardEvent.key values 
defined explicitly in uievents-key using a specially defined term such
 as 'functionally-defined values', or 'reserved values', or some such 
term that clearly indicates what they are and looks like a technical 

Actually https://w3c.github.io/uievents-code/#functional-key contains 
a definition for 'functional keys' that might work(?)

A side benefit of this would be that you could then talk about 
'printable characters' as being the set of character produced by keys 
that are not within the set of functionally-defined values.

Another example of this is in 

where the definition of KeyboardEvent . key says

> key holds the key value of the key pressed

Does that just mean 'the value produced by the key', or is it 
referring to the technical term 'key value' ?

See https://github.com/w3c/uievents/issues/117
Received on Friday, 16 December 2016 14:05:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:11 UTC