Decide on consistent UI pattern for user confirmation

[jotaen4tinypilot]

I don’t think we follow a deliberate pattern in the UI as to when we require confirmation after button clicks in dialogs. E.g.:

• In the upcoming “Static IP” feature, we’ll have a separate confirmation prompt before removing the static IP address.
• In the <security-dialog> component, we have a confirmation prompt when toggling off the auth requirement.
• Apart from that, I don’t think we have such a confirmation in any of our other dialogs, including the ones that carry out destructive and potentially “harmful” operations, such as:
  • Removing individual users
  • Disabling the HTTPS enforcement
  • Changing the hostname (which causes a device reboot)
  • Removing disk images (which are potentially very slow to upload)

Not having any confirmation for these kinds of operations actually makes me feel slightly uneasy. (I’m not sure how e.g. customers feel about that, though, or whether we have ever received “angry” feedback about this.)

In any event, I think we should define our desired UX pattern for user confirmation in the style guide, and then roll out the rules in the entire UI.

UI-wise, there are different patterns for user confirmation. Apart from the aforementioned separate confirmation step/prompt, there are also more light-weight patterns we could consider.