4 ms·
A lot of people still put them in forms. They just intercept the form submit to do with as the please. No putting them in a form also breaks accessibility
by nerdbaggy 6y ago
A lot of people still put them in forms. They just intercept the form submit to do with as the please. No putting them in a form also breaks accessibility
- Someone1234 6y agoAnd a lot of sites don't. "This breaks a ton of things but not everything" isn't a good attitude to browser compatibility, particularly from a browser that already has a small market share. > No putting them in a form also breaks accessibility Nope. Screen readers have no concept of <form> fields, nor any concept of how the piping works below the surface when a <button> is pressed. I run a screen reader every single day.
- renewiltord 6y agoAm I missing something? This seems less surprising than the alternative.
- jeroenhd 6y agoOne breaks the expectations of users, the other breaks the expectations of developers. On a website full of developers you'll probably see a lot more from one side than from the other.
- Someone1234 6y agoI'm pretty sure being able to input text longer than the maximum allowable text into a field breaks user's expectations too. Users don't "win" because you made how a site works more confusing. Their justification for this change is the only user-win (password truncation), and they could have trivially restricted this to passwords then body is hurt.
- edoceo 6y agoUsers don't expect the length limit! that info isnt presented to them until the text is over-long and the clue is: Surprise! Truncate w/o warning. On more than just password fields.
- nerdbaggy 6y agoInteresting, I really hate it when I press enter and it doesn’t submit the form.