Replies: 2 comments
|
A second case for the seam, from a different direction than the mark vocabulary Building a plugin block catalog against One category of content could not make that crossing. Designed inline emphasis, That is the part worth adding: the cost is not only that a custom mark fails to Not asking to reopen #2430 — the split described there makes sense, and this is |
|
Converted this to a discussion as it is a feature request. |
Uh oh!
There was an error while loading. Please reload this page.
@emdash-cms/admin@0.33.0registers a fixed inline mark set insrc/components/PortableTextEditor.tsx: bold, italic, underline, strike, code, link, subscript, superscript. Highlight and text colour are absent, and@tiptap/starter-kit@3.29.2does not bundleextension-highlight,-text-styleor-color.They can't be added downstream. Per #2430 there is no plugin seam to register a TipTap mark, and read-back conversion drops unknown marks. Note #2430 cites the core package's converters;
@emdash-cms/adminhas its own copy —convertPTMarks(line 1281) drops any bare unknown mark — so fixing core alone won't fix the admin editor.Ask: add
HighlightandTextStyle/Colorto the built-in set, or ship the seam proposed in #1996/#144 and preserve registered custom marks on read-back.All reactions