Less Confirmations Option #1043
Replies: 4 comments 1 reply
|
Yes, I would really like to have fewer confirmation dialogs. |
|
Yes. Please don't force us to double click what we expect is a single click. If we click a button it means we want to click the button. No need for "press again to confirm?". If you want to warn us of shooting ourselves in the foot write a red text that says "do you want to shoot yourself in the foot?" in the modal. But if we decide to shoot ourselves in the foot, let us shoot. Nothing is more aggravating than having to stab yourself twice just so you manage to get it done once. And. This. On. Every. Button. |
|
We need a better balance here. Starting a stack update from the stack list takes 7 clicks plus a paste—way too much. We just need consistent confirmations for destructive actions. Deleting something: absolutely. Restarting a stack: debatable. But the copy/paste confirmation should go, unless there are actions that actually delete files. Deploy does not. |
|
I'm not too fussed about the double click confirm (though would gladly disable), but having to type things in is such a pain. As said above I'm fine with doing so for deletions. |
Uh oh!
There was an error while loading. Please reload this page.
I'd love to completley disable the confiramtions. I have
disable_confirm_dialog = truealready, but I find it way to much.And here is some irony, I've wiped my entire directory before without warning (having to click/type, there is a written warning" when re-cloning and I didn't have trailing slash.
But overall, I would love to never have to type a confirmation or double click. I'd love that to be an option on top of the above option, like "no_confirmation_ever=true"
All reactions