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
In rich text mode, having an horizontal rule after a source fence, if you move the cursor down ↓ it visually pushes the
down one line each time you go over it.
There is also no way to get beneath the HR element when it is the last element in the doc.
To Reproduce
MD mode, enter this text:
```
text in fence
```
---
Switch to RT mode. Click in text, then down arrow
Observe, a new line is inserted
Root cause is not that you cant get past the HR in RT mode, since when there is more text beneath it, the link still appears.
Expected behavior
Should be able to move beyond the HR to go past it, the way that can be done when it is preceded by regular text and not a fenced code block
Desktop (please complete the following information):
Windows 11 Chrome 103
yellis
changed the title
bug(richtext)
bug(richtext) Extra line inserted when advancing past code block to following HR element
Jul 17, 2022
yellis
changed the title
bug(richtext) Extra line inserted when advancing past code block to following HR element
bug(rich-text) Extra line inserted when advancing past code block to following HR element
Jul 17, 2022
Describe the bug
In rich text mode, having an horizontal rule after a source fence, if you move the cursor down ↓ it visually pushes the
down one line each time you go over it.
There is also no way to get beneath the HR element when it is the last element in the doc.
To Reproduce
Root cause is not that you cant get past the HR in RT mode, since when there is more text beneath it, the link still appears.
Expected behavior
Should be able to move beyond the HR to go past it, the way that can be done when it is preceded by regular text and not a fenced code block
Desktop (please complete the following information):
Windows 11 Chrome 103
Additional context
https://meta.stackexchange.com/a/380438/51
The text was updated successfully, but these errors were encountered: