Make "Create" or "Update" the first button, not "Cancel"

[twomice]

Having Cancel as the first button causes the form to cancel when the user hits Enter, which is an odd experience.

[michaelmcandrew]

Rather than switch the order, I think we can specify which one is the default (I think that having cancel on the left is fairly standard practice)

[twomice]

Having "cancel" as the last option is common throughout CiviCRM. I can't think of an example where that's not true.

[michaelmcandrew]

Hey,
That's true. I was thinking of every other UI in the world :) Can we compromise on having update as the default action?

[twomice]

If you're asking me, I'll advocate for consistency with the main platform.

From Jakob Nielsen:

Either choice has good arguments in its favor, ...

... it's best to follow the platform GUI standard. Applying consistent design that follows user expectations saves people much more time (and many more mistakes) than doing something that might be a tiny bit more optimal for your application but introduces an inconsistency. ...

• Windows puts OK first
• Apple puts OK last

Maybe you're usually working on a Mac? I hadn't thought of that.

Drupal puts OK first:

I couldn't find a Cancel button in WordPress, so no example there.

So my argument would be: Windows and Mac have their own way of things, but inside the browser, inside Drupal, inside CiviCRM, the consistent thing is to put OK first and Cancel last.

[michaelmcandrew]

I am using Linux - most seem to be on the right but I don't have strong feelings and agree that we can/should follow the CiviCRM standard.

[twomice]

Yay for Linux! Interestingly, I'm noticing it's pretty inconsistent on my Ubuntu machine, sometimes left sometimes right. But anyway...