3 ms·
Awesome! Thank you for this. Would you be able to upload a video or maybe add more context in a Github issue? It's really difficult getting Android right. The
by trueadm 4y ago
Awesome! Thank you for this. Would you be able to upload a video or maybe add more context in a Github issue? It's really difficult getting Android right.
The combination between browser + keyboard + OS version + keyboard language, it just makes it so much harder than it should be for Android. So any additional context you can provide will be a MASSIVE help. :)
- hiimshort 4y agoAdded an issue here: https://github.com/facebook/lexical/issues/1699 https://github.com/facebook/lexical/issues/1699 And, as a side note, great work on this project. I had previously built a wysiwyg system from Slate and a custom plugin system; Lexical seems like a solid progression and has some interesting ideas like using React components the way it does to facilitate editor plugins. May have to try creating a Preact wrapper so I can use it in my projects.
- netghost 4y agoWhat's your approach to Android support? Are you relying on mutation events, `beforeinput`, something else? I built a really solid android adapter (after spilling gallons of tears) for our Draft.JS fork, and might have a few tips if it's helpful.
- zurfyx 4y agoWe listen to a few typing related events and do some computation from here: keydown, input, beforeinput. Android, contrary to any other device, mostly relies on composition so Lexical makes sure to handle and flush these events accordingly. If you're curious, this is where it all starts - https://github.com/facebook/lexical/blob/main/packages/lexical/src/LexicalEvents.js https://github.com/facebook/lexical/blob/main/packages/lexic...