The current trend is to find and expose the low-level primitives that let developers build their own tags, so that instead of needing more features added to <te

The current trend is to find and expose the low-level primitives that let developers build their own tags, so that instead of needing more features added to <textarea> you can build an element that does everything <textarea> does and more. Then you are not constrained by the W3C process or decisions. Web Components plus the Selection and Range APIs get you most of the way there for <textarea>. Unfortunately, I've found them to have different bugs in various browsers, probably because they're not used so much, but fixing these APIs opens up a lot more than just better <textarea>. https://developer.mozilla.org/en-US/docs/Web/API/Range https://developer.mozilla.org/en-US/docs/Web/API/Range https://developer.mozilla.org/en-US/docs/Web/API/Selection https://developer.mozilla.org/en-US/docs/Web/API/Selection Custom elements can't participate in <form>s easily yet, which should probably be fixed, but a lot of apps are skipping form submission for XHR calls anyway.