UX/HIG: Form handling

[Letterus]

What Happened

I expierence inconvenient and/or inconsistent form handling. I describe below what I'd expect. As I found no repo for UX/HIG issues I'm filing it here. Please move it or tell me where to file this correctly.

Expected Behavior

Coming from a very user friendly proprietary operating system I expect this behaviour from a form:

1. When I start typing the first input field applicable already is selected (already applied) (also called: first responder).
2. When I hit the escape key the current action/form always is canceled (not yet applied).
3. When I hit the return key the current action/form always is submitted if submit already is applicable (not yet applied).
4. When I use the tab key form input fields are selected one after the other starting with the one I'm currently typing in (already applied).
5. When I reach the button input fields using the tab key then first the default action (submit) should selected (if applicable) and the cancel action button should only be selected after one further tab (not yet applied).

I expect these rules to be obligatory HIG for all app forms and to be implemented via technical defaults as soon as possible.

[cassidyjames]

These could be clarified in the HIG at elementary/hig, and separately specific issues will need to filed against the apps where you see them not behaving in this way. Gonna mark this as Needs Design for now though for UX discussion.

[Letterus]

Thank you for your reply, @cassidyjames. Somehow I did not notice the hig repo. Should I repost these observations?

[cassidyjames]

@Letterus I can transfer this issue directly. 😄