Release notes · September 4, 2026

RichTextEditor 2.7.0

Core 2.5.8: bold, italic and strikethrough can choose their tag; indentation stops pretending to be a blockquote; a new inline-code button.

Latest
2.7.0

Bold, italic and strikethrough can now choose their tag New

The browser’s own execCommand always writes <b> and <i>, while this editor’s Markdown shortcuts (**bold**, ~~strike~~) write <strong>, <em> and <s>. One document could carry both spellings depending on how the author applied the format, and nothing let you pick.

New boldTag (b | strong), italicTag (i | em) and strikeTag (s | strike | del) normalise the output of getHTMLCode() in both directions, which also makes those two paths agree. Defaults are b, i and s, so existing output is unchanged.

Applied to the saved HTML rather than the live document on purpose: renaming nodes mid-edit collapses the user’s selection. There is deliberately no underlineTag — the only alternative to <u> is <ins>, which asserts that text was inserted, and a formatting button has no business making a revision claim on the author’s behalf.

Indent and outdent no longer emit blockquotes Fix

Indenting wrapped text in <blockquote style="margin:0 0 0 40px"> — a browser artifact, not a quotation. Word export mapped that to the built-in Quote style, so indented paragraphs arrived in .docx as styled quotations complete with a quote bar.

Indentation is now its own concept: margin-left (or padding-left via the new indentUseMargin), step size via indentation, right-to-left aware per block. Lists still nest structurally, existing indent-blockquotes unwrap on outdent, and a real <blockquote> is left alone.

Inline code New

A toolbar button for <code> spans, separate from the existing code-block insert.

Markdown export covers sub, sup, mark and ins Fix

Previously dropped to plain text on export.

Install or upgrade

Grab the latest via npm:

npm install @richscripts/richtexteditor@latest

Feedback & issues: support@richtexteditor.com