91–100 of 111 posts
This looks staggeringly brilliant. I was searching for something like this recently but ended up rolling my own using a block-based OT to local server and diff sync to remote ones. I’m reading the system guide and nodding along. It’s super validating to see the similarities and contrasts.
Getting that WYSIWYG editor up and running was a major stumbling block that I overcame to get my school newspaper a PHP-Nuke site ~25 years ago. It is insane that there isn't a web standard implementation for this passed 15 years ago.
There is contenteditable, which is what all these (Wordgard, ProseMirror) are fundamentally built on. The rest is just the UI, and interop with systems that don't desire arbitrary HTML as input.
That's a hell of a "just", as anyone working on such projects will tell you. It's super super hard to get this right.
I don't like WYSIWYG on the web. You do a long and tedious formatting of a forum post, then close the tab and it's all gone. I prefer to use a local text editor then Ctrl+V into web form. Which I can with markdown
Why this over Lexical by Meta?
Wordgard failed that test. Inputs coming from autocorrect or the keyboard suggestions are swallowed and delete the partially typed/misspelled word.
One area every editor has failed for me is a very basic one: can I type a full sentence in the editor using my iPhone? Wordgard failed that test. Inputs coming from autocorrect or the keyboard suggestions are swallowed and delete the partially typed/misspelled word.
There have been several efforts over the last couple decades to add a proper rich text element to the web. I don’t know why they have all failed - I guess it’s a large, complex and thankless task. It’s a pity. Proper native rich text support is one of the web’s big blind spots. It’s a problem native platforms have solved decades ago.
One area every editor has failed for me is a very basic one: can I type a full sentence in the editor using my iPhone? Wordgard failed that test. Inputs coming from autocorrect or the keyboard suggestions are swallowed and delete the partially typed/misspelled word.
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…
One area every editor has failed for me is a very basic one: can I type a full sentence in the editor using my iPhone? Wordgard failed that test. Inputs coming from autocorrect or the keyboard suggestions are swallowed and delete the partially typed/misspelled word.
Both mobile Safari and Chrome Android do a ton of weird things that their desktop siblings don't, and play loose and fast with standards, so getting things to work correctly there tends to involve a long tail of hacks. Wordgard will get there but the focus before this first release has been on architecture.
One area every editor has failed for me is a very basic one: can I type a full sentence in the editor using my iPhone? Wordgard failed that test. Inputs coming from autocorrect or the keyboard suggestions are swallowed and delete the partially typed/misspelled word.
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…