Glad to see Tiptap getting more attention. I've used 1.0 and 2.0 and they've both been great to work with. However one GIANT roadblock in the project I was working on was the inability to create custom inline components, like say a link with inline buttons for removing/changing the url. I believe there still isn't support for this type of functionality.
Switching Rich Text Editors, Part 1: Picking Tiptap
41–50 of 54 posts
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#42Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#43Are all these editors based on contenteditable? https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Edit...
The prosemirror based ones are. I suspect the other ones are as well.
You're right. Slate, Quill.js and ProseMirror-based use contenteditable. Hacking browser for custom cursor (similarly as Zoho Docs does [0]) is quite hacky and often leads to more problems than advantages it provides.
[0]: I suggest you to take a look in Chrome debugger how it works. Quite funny piece of code. It is written in jQuery + vanilla JS, so it will be very easy to spot the whole algorithm.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#44> We took a chance that Slate would support more browsers and its API would remain stable (despite the maintainers strongly suggesting that both might not happen!). Unfortunately, our gamble didn't pay off, and the maintainers introduced significant breaking changes to the API and document model… You have been warned…
Not only maintainers introduces significant breaking changes, but then they have also lost interest in a whole project that lead to change of ownership (Ian doesn't commit much to Slate). AFAIK, Sunny is now still the main maintainer.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#45Thanks for submission! Very timely. Been searching for a stable and flexible editor (or rather a tool to build such an editor) and Tiptap looks like a good candidate. I was also considering Slate, but have found this rather annoying bug https://github.com/ianstormtaylor/slate/issues/4833 , which is surprising as it doesn't look like some rare edge case, and breaks something that seems to be like basic functionality f…
As a person, who lost some time to dive into Slate.js internals, I can say those issues will pop up more often and often. There are so many moving parts that makes pushing a fix problematic. It is a like pipe having tens of leaks, but you have only a duct tape that won't be enough for all holes. It is great there are still some people who take care this project seriously, and it has very nice unit tests to reproduce faulty scenario.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#46Earlier quoted context omitted.
> Ah, the joy and horror of rich text editors. The problem: there is no money to be made in writing software libraries these days, no matter how much a working solution is needed. So sadly, we're going to be stuck with all these suboptimal solutions for many years to come.
Maybe that's true. A lot of people tried the RTE stuff, and Basecamp/37Signals came close with a solution (I forgot the name). I guess it's a hard problem by definition, dealing with copypasted stuff from Word, dealing with browsers, etc. After using my simple Markdown solution for some years now, I came to appreciate the bare basic style of it. But it's not for every use case.
It‘s called Trix and I‘ve switched from Trix to TipTap because the whole plugin system works way better. And having the ability to process the document programmaticaly (TipTap = JSON, Trix = HTML) has opened a lot of possibilities for us.
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#47Glad to see Tiptap getting more attention. I've used 1.0 and 2.0 and they've both been great to work with. However one GIANT roadblock in the project I was working on was the inability to create custom inline components, like say a link with inline buttons for removing/changing the url. I believe there still isn't support for this type of functionality.
If I follow you, I think this is unfortunately a limitation of ProseMirror witch is the underling library TipTap is built on. From memory they haven’t completed it due to issues with how browsers handle text cursors in online nodes.
It’s a year since I last tried something similar and I think I ended up layering elements on top of where I wanted them from outside the editable element in combination with marks.
Don’t take my word for it though as a little out of practice with TipTap, it and ProseMirror are awesome though!
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#48Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#49When evaluating rich text editors for the note-taking app I started about a year ago (https://notabase.io), I ended up going with Slate because of its flexible schema and customizable plugin architecture.
I sort of regret that choice now. I ran into a lot of bugs when integrating it which I had to manually work around; issues go months without being addressed; and there still isn't good cross-platform support, especially for Android. With a more active contributor base, Slate could be a fantastic library, but I get the feeling that it's in maintenance mode now, with not many major changes in the past year and a v1.0 still far in the future.
Tiptap looks like it might be a good choice now, but I find it off-putting that I can't insert links in the demo editor on Tiptap's website (https://tiptap.dev), especially for my use case (a note-taking app whose core concept revolves around links).
Re: Switching Rich Text Editors, Part 1: Picking Tiptap
#50I use TipTap as a rich text editor in my open-source weekly journaling app.[0] One of the big gotchas I've had with TipTap is that it's extremely sluggish once you get to more than 300 words or so and you're using different formatting options. There's a multi-second delay between typing the word and the text appearing in the screen. The APIs are pretty nice, and I was able to convert to/from Markdown with it easier t…
Are you sure that it's not something else interfering with TipTap? Their long demo https://tiptap.dev/examples/book which has 200,000 words was still very responsive.
It's possible. I write with a lot of bullet points and formatting, so I might be hitting one of their edge cases.