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
Joplin version: e40d733
Platform: Mobile
OS specifics: iOS 15.6.1
Steps to reproduce
Disable auto-suggestions
Enable the beta editor
Edit a note
Show the keyboard
Describe what you expected to happen
The markdown toolbar should be just above the keyboard, like it is on Android.
Possible solution
Add a setting to enable/disable additional space below the toolbar
In the markdown toolbar PR, it was observed that some iOS devices have keyboards that overlap the toolbar. My phone appears to be the opposite -- the toolbar, even without the additional padding, is well above the keyboard.
Wrap the toolbar in a KeyboardAvoidingView -- this seems to have the same issue as manually adding padding. Regardless, the screen is already wrapped in a KeyboardAvoidingView.
Wrap the toolbar in an InputAccessoryView. We're using a WebView to edit text. As such, it seems that we can't use an InputAccessoryView because it requires an inputAccessoryViewID property.
Make the markdown toolbar draggable -- moving it up/down when the keyboard is visible adjusts the space below it.
Move the markdown toolbar to the top of the screen.
The text was updated successfully, but these errors were encountered:
Environment
Joplin version: e40d733
Platform: Mobile
OS specifics: iOS 15.6.1
Steps to reproduce
Describe what you expected to happen
The markdown toolbar should be just above the keyboard, like it is on Android.
Possible solution
Wrap the toolbar in a KeyboardAvoidingView-- this seems to have the same issue as manually adding padding. Regardless, the screen is already wrapped in a KeyboardAvoidingView.Wrap the toolbar in an InputAccessoryView. We're using a WebView to edit text. As such, it seems that we can't use an InputAccessoryView because it requires aninputAccessoryViewID
property.The text was updated successfully, but these errors were encountered: