You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When setting a simple content string containing the < or > chars but not containg any other Markdown-specific syntax, such as "a > b" for example, the editor renders the escaped versions > and <
To Reproduce
In the useEditor hook add the following extensions:
Set the content using editor.commands.setContent('a>b', false, { preserveWhitespace: 'full', });
The editor renders the escaped characters instead of the <, > chars:
Expected behavior
I'd expect the <, > chars to be rendered instead of their escaped versions.
Desktop (please complete the following information):
OS: Mac OS Sequioa 15.1.1
Browser: Chrome
Version: 131.0.6778.71 (Official Build) (arm64)
Additional context
Interestingly, adding any Markdown-syntax to the content will cause the content to be rendered as expected editor.commands.setContent('*italic* a>b', false, { preserveWhitespace: 'full', });
will render:
The text was updated successfully, but these errors were encountered:
Describe the bug
When setting a simple content string containing the < or > chars but not containg any other Markdown-specific syntax, such as "a > b" for example, the editor renders the escaped versions
>
and<
To Reproduce
useEditor
hook add the following extensions:editor.commands.setContent('a>b', false, { preserveWhitespace: 'full', });
Expected behavior
I'd expect the <, > chars to be rendered instead of their escaped versions.
Desktop (please complete the following information):
Additional context
Interestingly, adding any Markdown-syntax to the content will cause the content to be rendered as expected
editor.commands.setContent('*italic* a>b', false, { preserveWhitespace: 'full', });
will render:
The text was updated successfully, but these errors were encountered: