Do not use browser confirm windows for destructive actions
Problem to solve
Emphasize possibly destructive actions being made the user, such as deleting data
Further details
It would be nice if GitLab did not use the native browser confirm
window for possibly destructive actions, like deleting group labels.
In my specific case I’ve seem to have developed a “blindess” to native confirm messages since I’m use to seeing those mostly on spam websites and then to want to get rid of them as fast as possible. So when GitLab uses confirm
windows I tend not to give my actions as much consideration as I should, especially if I’m distracted or tired.
Proposal
Use custom confirm windows/modals for destructive actions, like GitHub has done.
What does success look like, and how can we measure that?
More qualitative than quantitative, but users like me that have developed some blindness to native confirm windows will take more time to consider destructive actions they would be about to make. So, decreasing the number of “regretful” actions in GitLab.