Ran into this one before, but couldnāt figure out whatās going on after lots of investigation.
We found that after hitting Enter twice, if you use Backspace once to go back, it will work the next time. Does look like thereās some invisible characters in thereā¦
This is also happening when making new lines in the item itself, with Ctrl+Shift+Enter. One has to press Ctrl+Shift+Enter twice in order to make a new line. But similarly to in notes, after the first try, subsequent attempts will succeed.
I see something similar in Firefox on Linux. When I type something in a note and press Enter the cursor looks like it stayed at the end of line and didnāt go to the next line. But if I actually start typing something else - the letters appear on the second line as expected. So a single Enter press works, it just doesnāt look the part.
Yes, it does. If you press Enter twice the cursor is shown at the beginning of the second line but the typed text will actually appear on the third one. But if you press Backspace then it starts behaving like normal. Up until you leave that note =).
I have a similar but slightly more annoying issue, as the same(?) bug ends up with my note being deleted. I can of course just undo, but with the way Iām using it, Iām finding myself having to undo once per note (as you mentioned, after going back it works the next time within the same note).
In short:
Write first line of note
Press enter ā cursor remains on first line as mentioned by @drichli (continuing to type also continues on the first line, unlike for @dvasyukova, but later doesnāt lead to the issue of notes being deleted; see attempt 1)
Press enter again to move cursor to second line
Press tab to indent second line ā cursor appears indented, but on 3rd line
Press delete ā cursor goes to beginning of 3rd line
Press delete again ā cursor goes to beginning of 2nd line
Press tab to indent second line ā first note completely deleted and replaced with a tab, leaving a blank note with two tabs in a row on line 1
Environment:
Chrome Version 59.0.3071.115 on MacOS 10.12.6
Hereās a screenshot thatās potentially more clear.
We recently redid how we handle new lines, so maybe @Shida is the best person to look at this.
Also @Rachael, could you please verify the issue is still present after youāve disabled all Chrome extensions like Grammarly? Chrome extensions that do text manipulation easily conflicts with Dynalist, and itās impossible for us to debug crazy behaviors under that situation. Thanks in advance!
@Erica, thanks for the response! I donāt have anything like Grammarly, but I did try disabling all extensions (as well as using incognito mode) and still experience the same issue.