4 ms·
It's replacing any previous web text editor UX components that we had in the past (likely DraftJS). We're also building Lexical for iOS which is slowly rolling
by trueadm 4y ago
It's replacing any previous web text editor UX components that we had in the past (likely DraftJS). We're also building Lexical for iOS which is slowly rolling out across iOS devices too.
- andrewshadura 4y agoWell, I want the previous editor back. In fact, just give me a text area. The current editor breaks the selection and, in turn, the clipboard manager, it doesn't work well with Compose and dead keys, and it sometimes ties itself into a knot, and the text can't be edited anymore.
- danuker 4y agoWhen pasting links stopped working for me is about when I stopped using Facebook. It's 2022 and we're reinventing every wheel, but in the browser. GitHub has a Markdown editor with a paste handler (converting tables and such). It once had a bug. I had to disable handlers in the browser to be able to paste.
- dbbk 4y agoA textarea would not work
- jamespetercook 4y agoVery interested to know if there are any plans to support React Native? I’ve been struggling to find a good library that doesn’t require a web view.
- acywatson 4y agoIt's under consideration, but as of now we need native support for iOS and Android first. React Native doesn't currently support contentEditable.