Currently, our docs for KeyboardEvent.key and KeyboardEvent.code try to provide direct maps of each major OS's keycodes to the values that result from pressing them. This makes for lots of tables with a lot of repetitive information.
I'm looking to simplify this. How useful is it to have all of these tables, rather than just a list of the key values (or code values, for KeyboardEvent.code) and what they mean, and leaving the mapping of the hardware code to the standard values to OS-level documentation? I can continue to provide the per-OS information (I'd kind of like to -- but I have to consider the time involved), but if it's only marginally helpful, it may not be worth the maintenance cost, so I'd like to see if there are opinions on that. What I'd like to do is provide tables broken down by key category (navigation, whitespace, modifier, etc) like the spec does, because I think that's really handy, with tables that have columns for the key value, description, and (if useful) a column for each of the major platforms. Any thoughts appreciated! -- Eric Shepherd Senior Technical Writer Mozilla Developer Network <https://developer.mozilla.org/> Blog: https://www.bitstampede.com/ Twitter: http://twitter.com/sheppy Doodle: http://doodle.com/the.sheppy _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
