4 ms·
Disabling copy paste on the field that specifies the resource isn't a solution though, as that only increases the risk of typos.
by contravariant 8y ago
Disabling copy paste on the field that specifies the resource isn't a solution though, as that only increases the risk of typos.
- samatman 8y agoAn example of what GP is talking about is Github’s “type the name of the repository to delete it” workflow. Which I appreciate. A typo would just fail to delete, which is the correct response.
- Benjamin_Dobell 8y agoGithub does allow pasting though. The purpose of this input field isn't specifically to make the user type. It's simply to ensure they know the name of the repository they're deleting. Sure Github could (and do) display the repository name; but users are accustomed to just hitting next without reading written text. Input boxes (as opposed to buttons) requires user attention because the user has to know what content to place in the input field. Copying and pasting still meets this requirement as the user has to scan for the repository name (i.e. read) then copy and paste that into the field.
- afiori 8y ago> but users are accustomed to just hitting next without reading written text. This is why you should (almost) always offer undo for any action that would require a confirmation. A good balance would be Confirmation -> a window of time (5 seconds - 30 days) when undo is possible -> a slightly hidden menu for irreversible confirmation.