This was previously connected to right alt, which was confusing the
keyboard handling code into generating up events for this key when it
didn't match the expected values. This key is also configurable, and
only defaults to right alt in Ubuntu/GNOME.
Fixes https://github.com/flutter/flutter/issues/154053
Contains the merged physical key data from all the other sources. This file is regenerated if "--collect" is specified for the gen_keycodes script, or used as a source otherwise.
Contains the merged logical key data from all the other sources. This file is regenerated if "--collect" is specified for the gen_keycodes script, or used as a source otherwise.
A supplementary HID list on top of Chromium's list of HID codes for extra physical keys. Certain entries may also overwrite Chromium's corresponding entries.
Maps the web's key for modifier keys to the names of the logical keys for these keys' left and right variations.This is used when generating logical keys to provide independent values for sided logical keys. Web uses the same key for modifier keys of different sides, but Flutter's logical key model treats them as different keys.
Maps pseudo-keys that represent other keys to the sets of keys they represent. For example, this contains the "shift" key that represents either a "shiftLeft" or "shiftRight" key.
A list of layout goals, keys that the platform keyboard manager should find mappings for. Each key in this file is the key name of the goal, both logical and physical simultaneously, while its value represents whether the goal is mandatory. A mandatory goal must be fulfilled, and the manager will use the default value from this file if a mapping can not be found. A non-mandatory goal is suggestive, only used if the key mapping information is malformed (e.g. contains no ASCII characters.)
Maps a logical key name to the names of its corresponding physical keys. This is used to derive logical keys (from keyCode) that can't or shouldn't be derived from characterIgnoringModifiers.
Maps a pair of the web's key and location to the name for its corresponding logical key. This is used to distinguish between logical keys with the same key but different locations.
Maps a physical key name to a logical key name. This is used to when a keycode maps to multiple keys (including when the keycode is 0), therefore can only be told apart by the scan code.
Maps a name for GTK's modifier bit macro to Flutter's logical name (element #0) and physical name (element #1). This is used to generate checked keys that GTK should keep lock state synchronous on.
Maps a name for GTK's modifier bit macro to Flutter's physical name (element #0), logical name (element #1), and the logical name for the paired key (element #2). This is used to generate checked keys where GTK should keep the pressed state synchronized.
Maps the name of a keyval macro of a numpad key to that of the corresponding key with NumLock on. GTK uses different keyval for numpad keys with and without NumLock on, but Flutter's logical key model treats them as the same key.
Maps a logical key name to the names of its corresponding physical keys. This is used to derive logical keys (from keyCode) that can't or shouldn't be derived from characterIgnoringModifiers.
af3c91045b