Comment

Comment by jomkr

There is a subtle valid use-case.

On "change your password" screens, you don't want the second "confirm password" field to be pastle-able to stop this scenario.

1) User tries to type "mypassword" but enters "mypasswor" instead.

2) User copy-pastes "mypasswor" into "confirm password field"

3) User hits "submit".

Now when the user tries to login with "mypassword" it fails.

parent jomkr 9 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton