search

standardnotes / mobile

[Moved to https://github.com/standardnotes/app] Standard Notes for iOS and Android - https://standardnotes.com
GNU Affero General Public License v3.0
826 stars 112 forks source link

Keyboard does not activate when using Markdown Pro and Markdown Minimist #539

Open catwithbanana opened 2 years ago

catwithbanana commented 2 years ago

I'm on Android using the latest released version of Standard Notes 3.9.12 along with GBoard.

If I switch my editor to Markdown Pro or Markdown Minimist the keyboard disappears and no amount of tapping anywhere in the note brings it back, meaning I am unable to type or edit at all. Other extensions, such as Markdown Basic, work as expected.

This bug has persisted for several versions now. Please let me know if you need any further information for troubleshooting.

stefan-yas commented 2 years ago

What's your device model and OS version, @catwithbanana? Can't seem to reproduce this issue on my device. Do you know when the issue started, with which version of Standard Notes?

catwithbanana commented 2 years ago

I'm on a Pixel 5 running CalyxOS version 3.1.0 (Android 12). This issue goes back at least a month -- I unfortunately don't remember the exact starting time. It was happening when I was still on Android 11, though, so I don't think it's related to my recent A12 update.

With editors like Markdown Basic, when I click anywhere on the text the keyboard appears as expected for editing.

With Markdown Pro and Markdown Minimist, however, the only way to get the keyboard to appear and allow editing is to long-press somewhere until a word is highlighted. Then the keyboard appears for editing, though it's still a bit flaky and buggy -- the cursor sometimes hops around, causing edits to go in unintended locations.

I'm happy to provide logs, videos, or whatever else may help you fix this issue. Thank you for your help.

stefan-yas commented 2 years ago

I'm thinking this is likely due to your custom ROM. We haven't had any other reports of this behavior, so likely something to do with how the OS handles bringing the keyboard up or down. Perhaps it's a good idea to reach out the developer of the custom ROM to see if they can identify the issue.

dashrandom commented 2 years ago

Hi @stefan-yas , I can confirm this isn't a ROM specific issue. I'm using a stock Sony Xperia 5 III and experience the same behaviour. Let me know what logs would help or if a screen recording reproduction of the issue is required.