In 80% of use cases, truncating a field to a specified number of characters makes sense for teaser display modes. For those few use-cases where you actually want different content, what you really should be using is a different field.
Having these two concepts contained in a single field is confusing for users, and will become even more confusing when we introduce a Rich-text editor.
We may need to include some kind of an upgrade path for sites that were using the splitter before, but I think that could be done reasonably easily.
GitHub Issue #:
490
Recent comments
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5