pubuzhixing8

Will support soon

@ilya2204 Thanks for your feedback, I have understood the cause of this problem, I will give ideas as soon as possible.

Hi @ilya2204 I solved this problem by referring to the idea of slate-react, but this solution is a bit sloppy, and the current solution has some problems. The trigger timing...

Hi @ilya2204 I haven't reproduced the problem you mentioned (moving with the arrows / cutting text through the ctrl+x ), but the current way of doing it may indeed be...

@ilya2204 Amazing, I found the cause of the problem, a specific rendering template is used when the text ends with `\n` , so the browser's default rendering behavior cannot be...

> And maybe add more complex character input checks. Instead of `/[a-z ]/i.test(event.data)` something like `event.data.toUpperCase() != event.data.toLowerCase()` which works in most languages. Or perhaps add the ability to pass...

@RaulPROP I'm sorry to tell you that there are still basic input issues on this PR that have not been resolved. - [x] Pressing enter at the end(richtext demo) throws...

> Those two things works perfectly with my devices both on Chromium and Firefox (I have not tested this with iOS yet, but I will in the coming days). >...

> I just tested it on a mac (Mac mini w/ M1, macOS Monterey 12.1) with Chrome, Safari and Firefox and I can not reproduce any issue. > > Also...

> That branch is just to have a working version for the company that I work for. I'm glad to hear that, too.