A similar thing happens on Android all the time. Pressing Enter at the beginning of the line will break the existing line in half instead of inserting an empty line.
Are you using any 3rd party spell checkers or text manipulation program? It doesnāt happen for our testing Android device and if itās happening for everyone I think weād know by now!
Interestingly enough, this seems to be the culprit. I tried with the AOSP keyboard and Keepass4Android keyboard, and in both cases the new line was created correctly.
Switching back to Gboard, the wrong behaviour returns.
For the life of me, I canāt understand the relationship.
Me neither, because weāll never get to see their code to understand the interaction.
Generally extensions/plugins that manipulates text can do this kind of stuff, just like Grammarly (read above). When you press Enter, this extension/plugin may want you to do one thing (e.g. use the first auto-correct suggestion), whereas Dynalist wants to create a new item. When these two things act together, unexpected things can happen.
The problem with gboard (English, US version) creating new lines incorrectly happens here as well. As this is an app that comes with many android phones by default, and is my keyboard app of choice, is there any way you can still look into this? If you need me to, I can give you as much information about the problem as I can.
I have the same issue on my Google Pixel XL (default GBoard keyboard).
Iāve noticed the issue occurs if I press the enter button prior to a next word rather than immediately after a word. (eg: depending on where the space is).
For example:
This is a test
This is[enter] (before the space)
*Works fine.
This is [enter] (after the space)
*Duplicates the first following word/letter. So I end up with * aa test
Same at the beginning of a sentence. If I put a space before the text I want to bring down to the next line, then hit enter before the space it formats correctly. Otherwise it keeps the first word on the bullet and bumps down everything after that. So Iād end up with:
This
is a test
Even though I hit enter before the T.
Iāve noticed it for a while, I just avoided the error by adjusting my behaviour instead.
Hi, we have looked into the problem, but canāt reproduce the issue consistently. That is, we come across the issue randomly and rarely, but canāt identity a set of steps that will trigger this problem every time.
Thatād be the most valuable information we need to get the investigation and bug fixing going.
Also @NeedsCoffee you probably want to open another bug thread, since this thread is for the bug on the web version thatās caused by the interaction between the Grarmmarly extension and Dynalist.
Grammarly could have implemented their extension differently for each browser, which is likely the case because it deeply integrates with text editing.
Itās weird though, I think weāve heard Chrome users complain about this issue before. Maybe itās fixed recently?
