I have a dialog that allows the user to enter text to be processed.
Initially, there are two buttons: "Cancel" and "Assemble."
The latter button is the primary action (in Bootstrap, .btn-primary
).
Once the user enters text and presses "Assemble," they have the option to either make changes and "Assemble" again, or to complete the action (closing the modal dialog and doing processing).
Does it make sense for the button to complete the action to also be primary?
Here's a picture to demonstrate what I mean. The green success alert only appears after a user submits some valid code into the textbox and presses "Assemble."
My thoughts:
- Before the user first assembles code, "Assemble" certainly is the primary action.
- After the user assembles code, there really are two primary actions; either of the two buttons I've currently marked primary is a perfectly plausible next step.
- It would probably be weird to make the "Assemble" button no longer a primary action after being pressed—to change its primary status at runtime—right?
.btn-danger
, or is this bad form? – wchargin Jan 17 '15 at 20:15