keyboards property
Whether the entries under here are worth seeing with a keyboard up, head first, likewise.
A staging axis in previews and a policy in scenarios, and the reason
is that nothing in a preview focuses on its own: a form rendered cold has
no field selected, so the only way a matrix covers the smaller screen is
to cross it. A scenario taps the field itself and the keyboard follows,
which is why ScenarioProfile has no list like this one.
Empty means KeyboardMode.auto — exactly what the entry asks for, which
for most entries is nothing at all. [KeyboardMode.up] on a directory of
form screens is how a project says these are the ones where it matters.
Implementation
final List<KeyboardMode> keyboards;