All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
You received this message because you are subscribed to the Google Groups "ui-input-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ui-input-dev...@fuchsia.dev.
To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/ui-input-dev/CAGEh6bhXS5FVM3GLWugzxhegUzD2Wj-wthp9zCatCT339SB_BQ%40mail.gmail.com.
Thank you!Will do and will report back for posterity.
This may seem obvious, but I'll leave a few links here for the record.
Input2's definition of KeyMeaning was `SemanticKey`:
Which was based on W3C's named key attribute values:
The "reserved" block is an attempt to keep enum values together for same types of the keys, i.e. when a new modifier is added, it would be added in the "modifiers" block rather than get a new number at the end of the list.
So, no practical purpose, just long-term API health consideration.