-
-
Notifications
You must be signed in to change notification settings - Fork 833
Conversation
* suppress autocomplete when navigating through history * only search for slashcommands if in the first block of the editor * handle suffix returns from providers correctly * fix SelectionRange typing in the providers * fix bugs when pressing ctrl-a, typing and then tab to complete a replacement by collapsing selection to anchor when inserting a completion in the editor * fix element-hq/element-web#4762
* suppress autocomplete when navigating through history * only search for slashcommands if in the first block of the editor * handle suffix returns from providers correctly * fix bugs when pressing ctrl-a, typing and then tab to complete a replacement by collapsing selection to anchor when inserting a completion in the editor
if you want to escape a /, do it with \/ or just precede with a space
also make emoji autocomplete work again also remove the onInputContentChanged prop also slateify the onInputStateChanged prop
Does anyone even test their changes here!? New bug:
|
@makedir i think a full New issue would make more sense and mentioning the pr than writing that into one of the prs. (as afaik this change happend with more than 1 pr). Also as far as I remember I can write after emoji just fine (Windows 10 and Linux Arch) |
No I cant with Windows 10 client latest version (riot.im), example: "This is a test <3" If I press space after <3 nothing happens (cursor doesnt move), I cant write on and have to press enter. |
@makedir thats not a valid emoji in riot. Valid emoji would be something like: |
And? Than thats even two bugs. If I type <3 your client opens the emoticon box and wants to replace it with a heart, same as :-). If the box is open space doesnt work it seems. |
|
Also this was tested hundreds of times. Updates to the slate library since then likely introduced new issues. |
This PR replaces Draft with Slate, with the intention of fixing pretty much all of the RTE bugs we currently have available and making the composer feel much more snappy, polished and robust. The strategy taken is to 1) comment out everything Draft specific; 2) gradually go through porting each commented-out section to Slate, whose API is luckily relatively similar (albeit much simpler). Some things to note:
Current progress is:
Nice to have:
Optional: