Left/right navigation in conjugation view resets keyboard to alphabetical view instead of cycling conjugation sections

[catreedle]

Terms

• I have searched all open bug reports
• I agree to follow Scribe-Android's Code of Conduct

Behavior

Description:

When a user is in the conjugation view and presses the left or right navigation buttons to cycle through conjugation sections (e.g. Present → Past → Future), the keyboard resets to the standard alphabetical keyboard view instead of displaying the previous/next conjugation section.

Steps to reproduce:

1. Enable a Scribe language keyboard
2. Enter conjugation mode and search for a verb
3. When the conjugation view is displayed, press the left or right navigation button

Expected behavior:

The conjugation view cycles through the available tense sections (e.g. Present, Past, Future, Conditional) without leaving the conjugation view.

Actual behavior:

Pressing left or right dismisses the conjugation view entirely and resets the keyboard to the standard alphabetical layout.

Note: PR for this issue should ideally include tests to confirm the navigation behavior is working as expected.

Device type

Pixel API 33 emulator

Versions

latest

[mtiwari479]

Hi, i have experiece on android development, i want to debug it.
could you please assign it to me?

[andrewtavis]

Sure thing, @mtiwari479! Thanks for picking the issue up :)

[mtiwari479]

Thanks for assigning the issue!
I have started to looking into it. It seems the left/right navigation is triggering a keyboard reset instead of updating the conjugation state.

My plan is to:
identify where the keyboard mode is being reset
preserve the conjugation state during navigation
update the UI to cycle through tenses instead of exiting the view

i will update here once i locate the exact issue.

[andrewtavis]

Sounds great, @mtiwari479! Looking forward to the PR :)

[mtiwari479]

Hi @andrewtavis ,

I have implemented a fix for this issue and submitted a PR.

PR: #579

Please let me know if any changes required.

Thanks!

[andrewtavis]

Thanks @mtiwari479 Left a comment in the PR :)

[Cast43]

hi, this issue is closed?