i loaded it, tried deleting by swipping backspace, it did not work...
Wordgard: In-browser rich-text editor from the creator of ProseMirror
101–110 of 111 posts
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#102Earlier quoted context omitted.
The person who got inspired by prosemirror and built lexical is no more at meta. Go to the repository and you'll find it's already in maintenance mode. Its promise of cross platform extensible editor is unrealised yet. I'd pick prosemirror any day over Lexical.
You are wrong, Lexical it is not in maintenance mode and continues to receive commits from contributors. 24k stars and counting. https://github.com/facebook/lexical
We used Lexical intensively in my company (Crisp), and I can confirm it's definitely not in maintenance mode. What's super cool with Lexical is the package/extension system. For instance, we use the Lexical markdown package a lot; it's not the gold standard yet, but since we have a large user base, over the years we've made a few PRs to the Lexical team, and they approved/reviewed the PRs in 24 hours.
About WordGuard:
There is no community behind it; the guy building it clearly wants no AI involved and even has his own internal Git hosting system.
Finally, there is no single user on WordGuard.
I see virtually no reason to use Wordgard over lexical.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#103Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#104Earlier quoted context omitted.
The only scary thought is that all these important operations don't have a plan B if prosemirror, a software they don't write, don't own and presumably don't pay, goes away.
Many of them do pay. Also MIT-licensed software doesn't 'go away' all that easily. If a piano fell on my head tomorrow, interested parties would probably manage to continue development in a fork.
You are correct, but please watch out for falling pianos because we appreciate your work.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#105Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#106Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#107Earlier quoted context omitted.
Yeah I did a review of web based rich text editors a couple years ago. They all seemed fine on desktop, but on mobile every one I tried was junk. I couldn’t select. Autocorrect was broken. Tapping text didn’t move the cursor. Typing would stop working. The keyboard wouldn’t disappear when the element lost focus. And so on. There have been several efforts over the last couple decades to add a proper rich text element…
Meta has a text editor framework called Lexical that works well on mobile, I've used it at work before with great success. Perhaps you missed this one? https://lexical.dev/
This one if I recall also used by Payload CMS.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#108Earlier quoted context omitted.
Yeah I did a review of web based rich text editors a couple years ago. They all seemed fine on desktop, but on mobile every one I tried was junk. I couldn’t select. Autocorrect was broken. Tapping text didn’t move the cursor. Typing would stop working. The keyboard wouldn’t disappear when the element lost focus. And so on. There have been several efforts over the last couple decades to add a proper rich text element…
Fix your phone.
That's the ideal solution, because (it seems to me that) the issues that break rich text editors are caused by non-interoperable ad-hoc hacks from mobile browsers and operating systems. These rich text editors can work perfectly fine on desktop browsers, yet have countless buggy behavior on mobile. The editor side is not the main problem, it's the mobile side that needs to be fixed and better implemented in a consistent manner across platforms.
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#109[dead]
Re: Wordgard: In-browser rich-text editor from the creator of ProseMirror
#110Earlier quoted context omitted.
Fix your phone.
That's the ideal solution, because (it seems to me that) the issues that break rich text editors are caused by non-interoperable ad-hoc hacks from mobile browsers and operating systems. These rich text editors can work perfectly fine on desktop browsers, yet have countless buggy behavior on mobile. The editor side is not the main problem, it's the mobile side that needs to be fixed and better implemented in a consist…
I disagree. Rich text editors on the web are already a massive hack, because there aren’t any built in input elements which support rich text. There’s just contentEditable and textarea (plain text). There’s no such thing as “doing it properly” when it comes to rich text. Editors have to hack around what the browser provides via a million event handlers. And - surprise! Mobile browsers don’t expose the same events as desktop browsers.
The right fix is for browsers to have a real rich text element of some sort. Then editors wouldn’t need all their hacks. And mobile browsers would be able to behave correctly when you tap on some editable rich text.