3 ms·
Yes, who would have guessed that the <textarea> element, designed specifically for this use case and built into browsers for 3 decades, would be the most perfor
by akersten 1mo ago
Yes, who would have guessed that the <textarea> element, designed specifically for this use case and built into browsers for 3 decades, would be the most performant and behaviorally consistent way to implement editable text.
I'm kind of sad the author stopped shedding unneeded complexity there though... we're not really building a text editor yet, we're building a website with a fancy input field. If we want to build a proper text editor we must eschew the bloat that is the web browser too.
- notarobot123 1mo agoThe browser-standards-or-bust moment has past, hasn't it? If you want your app to work the same way across platforms, using browser defaults is not the way to achieve that. If you want users to have a consistent experience within their browser across the web, I get it, but that's not how the Web has worked for a long long time.
- snoopen 1mo agoSo we take a web browser and trim it down to only ever show a single <textarea> element you say? That's what I'm taking away from this. All the hard work for accessibility is already done then right?