joplin
joplin copied to clipboard
iPadOS floating / split / undocked keyboard almost entirey overlays note editor
Environment
Joplin version: 12.7.2 Platform: iPad Pro 10.5 " 2017 OS specifics: iPadOS 14.8.1
Steps to reproduce
- edit a note (preferably one with a lot of text for better effect)
- tap on a line in the note to bring up the keyboard
- if floating, split or undocked keyboard is used, any content below the keyboard will be covered white. Moving around the keyboard covers almost everything of the note editor white making it impossible to edit the note.
- you can resolve the issue by switching back to the normal keyboard at the bottom of the screen. (switching the keyboard is done by tap+holding on the keyboard down button in the bottom right and swiping up to the desired option before releasing)
Describe what you expected to happen
If any other keyboard than the default one that's at the bottom of the screen is used, you should still be able to properly use the note editing function.
Screenshots showing same note edit screen with and without floating keyword
normal keyboard - no problem:
floating keyboard - unusable edit screen:
There's also a video of this on an older issue report: https://github.com/laurent22/joplin/issues/5663 On this report other similar issues were linked, but those aren't the same - or at least the workarounds with the accessibility settings don't have any effect on my iPad - the issue remains the same.
Logfile
Nothing that I can see related to this showing in the log. That said, this seems to be an issue already reported on react-native: https://github.com/facebook/react-native/issues/29473 And there also seems to be workarounds posted that can help with the issue while it hasn't been fixed in react yet.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
The issue still remains after updating to Joplin 12.8.1 and I'm hoping that the workaround I linked to could be implemented if applicable to the reported issue.
Please try enablimg the beta editor.
On Android, there still seems to be an issue (editor content duplicated). Is this also true with iPadOS?
I already had the beta editor enabled. And the issue seems to only occur with the floating keyboard if the keyboard is moved around.
I'm not sure I see any issue with editor content getting duplicated.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
The issue is still present and in order to use Joplin I always have to switch to the normal keyboard instead of using the floating one (which I otherwise use on iPad).
Possibly-related: https://github.com/laurent22/joplin/issues/6682
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Still an issue.
This may have been fixed upstream (see https://github.com/facebook/react-native/commit/4b9382c250261aab89b271618f8b68083ba01785, which fixes a related issue). We use an unmaintained library that is blocking an update to the latest version of React Native. We will have to fix/migrate away from that library first.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Still an issue.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.