4 ms·
Stop trying to fix everything to be honest, so tired of encountering text inputs in React web apps that don't have system wide spellchecking because some engine
by whywhywhywhy 5y ago
Stop trying to fix everything to be honest, so tired of encountering text inputs in React web apps that don't have system wide spellchecking because some engineer decided they needed to roll their own input controls.
- BlueTemplar 5y agoSpellchecking is browser-wide ?
- jonhohle 5y agoOn macOS (ne OS X) system wide spellcheck has been available for over a decade.
- zeta0134 5y agoNot if a react component is reimplementing a textarea with JavaScript, which I've encountered in some enterprise apps. It's mildly infuriating, and breaks in lots of subtle ways.
- BlueTemplar 5y agoLike... from the ground up, placing pixels around to form letters ?!
- abdusco 5y agoNot really. It revolves around textarea not allowing rich inputs. That includes @-mentions, /-commands, block-based content builders etc. Textarea is laughably basic when it comes to adding interactivity to it, so the only solution is to use contentEditable[0][1], which is very difficult to work with or roll your own input[0], which makes OP angry. [0]: https://medium.engineering/why-contenteditable-is-terrible-122d8a40e480 https://medium.engineering/why-contenteditable-is-terrible-1... [1]: https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/contentEditable https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement...
- ryandrake 5y agoThank you. This is the solution. Stop "fixing" my scroll bar. Stop "fixing" my copy/paste behavior. Stop "fixing" my default fonts. Stop "fixing" navigation from element to element using tab. Stop "fixing" what links look like, what happens when I right-click, what happens when I use my mouse wheel, what happens when I resize my browser window. Just stop trying to be clever. Deliver your damn hypertext to my browser, get out of the way, and allow it to render.