Fix Ozone keyboard layout to handle German Neo 2.

ui/events/keycodes/dom/dom_key_data.inc

Index: ui/events/keycodes/dom/dom_key_data.inc
diff --git a/ui/events/keycodes/dom/dom_key_data.inc b/ui/events/keycodes/dom/dom_key_data.inc
index 52fce73d2eef8a50793e3f042ac831588da5e04b..e809b8dd32610f140b2ac0463b73e5bd2b29d401 100644
--- a/ui/events/keycodes/dom/dom_key_data.inc
+++ b/ui/events/keycodes/dom/dom_key_data.inc
@@ -64,6 +64,12 @@ DOM_KEY_MAP_DECLARATION {
   DOM_KEY_MAP("Symbol",               SYMBOL),
   DOM_KEY_MAP("SymbolLock",           SYMBOL_LOCK),
 
+  // Non-standard value corresponding to XKB keysym ISO_Level5_Shift,
+  // an additional printable-character modifier like Shift and AltGraph,
+  // used by such layouts as Neo (German) and Multix (French-Canadian).
+  //          Key                     Enum

[Wez, 2015/06/08 21:23:23]

The DOM UI Events spec guidelines (see
http://www.w3.org/TR/DOM-Level-3-Events/#keys-guidelines) don't allow for
"non-standard" |key| values - do we need to file a spec bug to support this?

[kpschoedel, 2015/06/08 22:30:02]

Yes, that section seems clear. (The |key| document
http://www.w3.org/TR/DOM-Level-3-Events-key/ alone seems ambiguous, though, with
phrases “… implementations must support, at a minimum …” and “… key values not
included here, which have become common since the publication of this
specification.”)

[Wez, 2015/06/10 23:24:48]

That does seem ambiguous - perhaps garykac@ can clarify & update the wording in
whichever of the two docs is correct wrt what the working group agreed.

+  DOM_KEY_MAP("ShiftLevel5",          SHIFT_LEVEL5),
+
   // ============================================================
   // Whitespace Keys
   // http://www.w3.org/TR/DOM-Level-3-Events-key/#keys-whitespace