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
bug1: The preview effect is incorrect when a blockquote is followed by an unordered title;
bug2: Based on the text of ‘* > 123’, the text after getMarkdown is rendered again and display abnormalities and getMarkdown abnormalities occur again.
To Reproduce
Steps to reproduce the behavior:
I used the wysiwyg example. the produce is:
Input ‘* > 123’ (Figure 0);
Click the wysiwyg button. At this time, problem 1 occurs: a meaningless p tag is added between the blockquote and the unordered title (Figure 1);
Click the return markdown button, and the mardown has more line breaks and spaces (Figure 2);
Click the wysiwyg button, and it turns into blockcode (Figure 3).
Click the markdown button (Figure 4)
Expected behavior
When I don't change the text content and only switch the wysiwyg and markdown buttons, the final markdown text obtained should be consistent with the previewed HTML.
Screenshots
Figure 0:
Figure 1:
Figure 2:
Figure 3:
Figure 4:
Desktop (please complete the following information):
OS: window11
Browser chrome
Additional context
In addition, there are some small wysisyg issues: For example:
When the cursor is clicked on the text of the unordered title, and then clicked on H1, it cannot be changed to the H1 style; but it can be changed in markdown mode;
In the unordered title, the first item li cannot be indented, but the indent icon does not turn gray, causing users to think that it can be clicked, but the click is unresponsive. It can be indented in markdown mode.
The text was updated successfully, but these errors were encountered:
Describe the bug
bug1: The preview effect is incorrect when a blockquote is followed by an unordered title;
bug2: Based on the text of ‘* > 123’, the text after getMarkdown is rendered again and display abnormalities and getMarkdown abnormalities occur again.
To Reproduce
Steps to reproduce the behavior:
I used the wysiwyg example. the produce is:
Expected behavior
When I don't change the text content and only switch the wysiwyg and markdown buttons, the final markdown text obtained should be consistent with the previewed HTML.
Screenshots
Figure 0:

Figure 1:

Figure 2:

Figure 3:

Figure 4:

Desktop (please complete the following information):
Additional context
In addition, there are some small wysisyg issues: For example:
The text was updated successfully, but these errors were encountered: