Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toolbar keys order is reversed #557

Closed
codokie opened this issue Mar 13, 2024 · 6 comments · Fixed by #574
Closed

Toolbar keys order is reversed #557

codokie opened this issue Mar 13, 2024 · 6 comments · Fixed by #574
Labels
contributor needed There will not be any progress without someone volunteering to work on this enhancement New feature or request

Comments

@codokie
Copy link
Contributor

codokie commented Mar 13, 2024

Describe the bug
The toolbar keys order is reversed when switching from an RTL to a LTR (or vice versa) keyboard layout.

To Reproduce
Add RTL layout (like Hebrew or Arabic) and a LTR layout (like English), then switch between the two layouts.

Expected behavior
The order of the keys should not be reversed because that makes it impossible to memorize the different locations of the toolbar keys.

Screenshots

Screen_Recording_20240313_222713_Joplin_1.mp4

App version
1.0-alpha1

Device (please complete the following information):

  • Model: Samsung Galaxy S24
  • OS: Android 14
@codokie codokie added the bug Something isn't working label Mar 13, 2024
@Helium314 Helium314 removed the bug Something isn't working label Mar 17, 2024
@Helium314
Copy link
Owner

Changing the layout direction according to active language has been default behavior of AOSP keyboard and its forks for more than 10 years.
If this should be changed, it must be optional.

@Helium314 Helium314 added enhancement New feature or request contributor needed There will not be any progress without someone volunteering to work on this labels Mar 17, 2024
@codokie
Copy link
Contributor Author

codokie commented Mar 17, 2024

Hi @Helium314, thanks for looking into this issue.
I have no experience with other AOSP keyboard forks but I'm fairly certain that the direction of the toolbar buttons is fixed between layouts in Florisboard, Samsung keyboard & AnySoftKeyboard.
(The direction of the toolbar buttons in Samsung keyboard is set according to the system language, and it does not change upon pressing the language change key)

@codokie
Copy link
Contributor Author

codokie commented Mar 17, 2024

I do not believe this is a desired behavior, I think it affects the user experience and makes no sense to not have a fixed position for such buttons.
Notice how the left and right arrow buttons order is switched when typing in the RTL layout: the right arrow is on the left, and the left arrow is placed on the right, which is very unintuitive.
I would greatly appreciate if this aspect could be improved, sadly I have no idea what source file is responsible for configuring the rendering of the toolbar buttons.

@Helium314
Copy link
Owner

I have no idea what source file is responsible for configuring the rendering of the toolbar buttons.

The toolbar views are handled in SugggestionStripView

@codokie
Copy link
Contributor Author

codokie commented Mar 18, 2024

Thanks for letting me know!
I created a pull request with a proposed fix which I've tested shortly.
I believe this is undesired behavior for anyone who types in both RTL and LTR layouts.

@codokie
Copy link
Contributor Author

codokie commented Mar 19, 2024

I checked the behavior of the GBoard toolbar and it matches the one currently set in the HeliBoard.
So you are right that this is not a bug, but I still think it's an inconvenience for those who frequently switch between LTR and RTL layouts.
I honestly don't know why Google thought this was a good idea. Maybe its because their keyboard has no navigation (left, up, right, down) toolbar keys.

@Helium314 Helium314 linked a pull request Mar 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributor needed There will not be any progress without someone volunteering to work on this enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants