E0207 Key or focus event no view hears
Words in italics are filled in when the compiler reports it, such as the element's name or the list of known ones.
Why
Lynx gives views no key events and only fields the focus: its keydown and keyup events (bindkeydown) exist only in its desktop builds and Lynx for Web, never on iOS or Android (checked against Lynx 4.2), and a field reports one key, Enter, as its confirm event. An on:key on a view that touch cannot reach another way (no on:press, no href, not a composite such as a tab list whose items are pressed), or an on:focus or on:blur on anything but a field, would never run on a phone (decision 0049). A spinbutton is not a composite: its arrow keys change its value, which touch never sends, so its on:key is heard only with buttons in its own group that touch presses and that move what its keys change both up and down, such as a stepper's − and +. A button counts when it is beside the spinbutton, or wrapped one level down beside it, and has on:press (a placed component's onPress). The buttons pair with it when their handlers between them move state the on:key writes both ways (one handler both ways, or one each way, through the file's own functions too), or when one's controls names the spinbutton's id. A button that does something else, or a Reset that sets the state to a value, does not count. Where the build cannot tell which way a handler moves the state (it calls an imported function or a prop's callback, steps by a prop whose sign is unknown, or writes the value as text), name the spinbutton with controls="…" on its buttons.
How to fix it
Let touch do the same with on:press or href, give the element a composite role, put buttons beside a spinbutton whose on:press handlers move what its on:key changes up and down, or say which they are with controls="…" naming its id (a handler that calls an imported function needs controls), or listen on the input or textarea.
In a terminal
duolith explain E0207