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
The same issue happens when pressing ">" to go to the next match.
The issue happens both when the soft keyboard is displaying and when it isn't.
On one device, when the keyboard is hidden, the bottom bar with the back/home/recent keys is translucent and the match can be seen (barely) behind the bottom bar.
Additionally, sometimes when the soft keyboard is visible and I press ">", the app somehow manages to scroll the top UI elements (file name, buttons, search field) up and out of view. Doesn't always happen though.
The text was updated successfully, but these errors were encountered:
I have gone through the checklist.
Affected app version
1.0.0
Also happens with SimpleMobileTools File Manager 6.15.4 and 6.16.1 (I don't have access to older versions to test).
Affected Android/Custom ROM version
Android 9
Affected device model
Android-x86 VM
Also a physical device
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Open a text file in the File Editor and search for some text that is offscreen.
Expected behavior
The view should scroll down to reveal the match.
Actual behavior
The view scrolls down, but not enough. I need to manually scroll down a bit more to see the match.
Screenshots/Screen recordings
See comment
Additional information
The same issue happens when pressing ">" to go to the next match.
The issue happens both when the soft keyboard is displaying and when it isn't.
On one device, when the keyboard is hidden, the bottom bar with the back/home/recent keys is translucent and the match can be seen (barely) behind the bottom bar.
Additionally, sometimes when the soft keyboard is visible and I press ">", the app somehow manages to scroll the top UI elements (file name, buttons, search field) up and out of view. Doesn't always happen though.
The text was updated successfully, but these errors were encountered: