Should all buttons require a confirmation dialog to prevent people from making decisions too hastily? Should we ensure all interactions have at least 100ms of latency so users don’t get mesmerized by a smooth experience? Maybe we should set a max color saturation so nothing looks too enticing. We also don’t really need box shadows or gradients, they’re clearly meant to mesmerize users into making bad decisions.

What an absurd and pointless precedent to set.

▲

kelseyfrog 2 hours ago | parent [-]

Either all buttons should require a confirmation or no buttons should. There is no in-between. There is no good judgement. There is no middle ground. All or nothing. It's black or white!

	▲	iamnothere an hour ago \| parent [-]
		Yes, buttons should only require confirmation if it’s a Required Confirmation Button as defined by Section 23554, but not if it’s an Exempt Button as defined by Section 23587. Of course, this only applies to Apps With Some Required Buttons as defined in Section 48994; Apps Always Requiring Confirmation as defined in Section 48985(b) must always request confirmation for every button. This applies only to Registered App Developers as defined in Section 15324. Unregistered App Developers should refer to Section 39406 for requirements. (Button itself is defined in Section 1144114(c), and is not to be confused with a Toggle, a Clickable Rectangle, a Clickable Text Container, or a False Button as defined in the same section.)