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
Inserting a new line (press Enter) on an empty line in a code block does not work correctly. To begin with it seem to do nothing, but if you start typing something afterwards it jumps to the new a line.
Steps to reproduce
Open new document
Insert code block
Move into the code block (ignore language identifier)
Press Enter
Press d (or any other letter)
Expected behavior:
A new line should be added in step 4, but it's not added until step 5 (line is added first and then the letter is added)
Actual behavior:
New line should be added immediately in step 4 (when pressing enter)
Example: Note: first part is repro, second part is some of the shenanigans mentioned below
I think my issue may be related.
Pressing Enter at the end of a code block mysteriously moves some characters from the curernt line to the next line. The issue resolves itself if I put the cursor at the end of a line that isn't indented and press Enter there. But it can reappear, and I don't have definitive STR.
Description
Inserting a new line (press Enter) on an empty line in a code block does not work correctly. To begin with it seem to do nothing, but if you start typing something afterwards it jumps to the new a line.
Steps to reproduce
Expected behavior:
A new line should be added in step 4, but it's not added until step 5 (line is added first and then the letter is added)
Actual behavior:
New line should be added immediately in step 4 (when pressing enter)
Example:
![mygif](https://user-images.githubusercontent.com/42169660/153574653-5e338761-4b5b-4340-8881-2c027f45b814.gif)
Note: first part is repro, second part is some of the shenanigans mentioned below
Versions
Additional notes:
There seems to be a bunch of issues with the code block that may be related to this problem such as:
But I think they may fixed by extension of fixing this bug. Let me know if you want dedicated issues on those though.
The text was updated successfully, but these errors were encountered: