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

bug(android): Keyboard is blinking in the background during the Keyboard changes using globe key #8534

Closed
1 of 8 tasks
bharanidharanj opened this issue Mar 28, 2023 · 6 comments · Fixed by #10017
Closed
1 of 8 tasks

Comments

@bharanidharanj
Copy link

Describe the bug

I noticed that while changing the keyboards using globe key, the Keyboard running in the Keyman application is blinking.

Reproduce the bug

  1. Install Keyman 17.0.78-alpha build in a Mobile device / emulator.
  2. Open Keyman application.
  3. Install additional keyboards like Khmer Angkor and sil_cameroon_azerty keyboards.
  4. Long press the globe key.
  5. Verify that the Language menu list opens.
  6. Change the language from the default keyboard to sil_cameroon_azerty keyboard.
  7. Here, the Keyboard running behind the language list menu blinks.
  8. Change the language from sil_cameroon_azerty keyboard to default keyboard.

Here, the Keyboard running behind the language list menu is blinking for a while.

I have attached the video(keyboardblinking.mp4) file for reference.

keyboardblinking.mp4

Expected behavior

Keyboard blinking should not happen If the keyboard changes using globe key.

Related issues

No response

Keyman apps

  • Keyman for Android
  • Keyman for iPhone and iPad
  • Keyman for Linux
  • Keyman for macOS
  • Keyman for Windows
  • Keyman Developer
  • KeymanWeb
  • Other - give details at bottom of form

Keyman version

17.078-alpha

Operating system

Android 11.0

Device

Redmi Note 8 Pro

Target application

No response

Browser

No response

Keyboard name

No response

Keyboard version

No response

Language name

No response

Additional context

No response

@mcdurdin mcdurdin added this to the Future milestone Mar 29, 2023
@mcdurdin
Copy link
Member

Relates to keyboard resizing and banner during keyboard switching, made more complex by async. Probably need to have a 'begin change' and 'end change' lock on refresh.

@darcywong00 darcywong00 changed the title bug(android): Keyboard is blinking in the backgroud during the Keyboard changes using globe key bug(android): Keyboard is blinking in the background during the Keyboard changes using globe key Apr 18, 2023
@darcywong00
Copy link
Contributor

From Sprint A17S11 sprint plan triage, we would've closed this one if dupe on #7161, but I don't see it, so moving to 17.0

@darcywong00 darcywong00 modified the milestones: Future, 17.0 Apr 18, 2023
@darcywong00
Copy link
Contributor

darcywong00 commented Apr 24, 2023

The blinking seems to mostly happen when going from a keyboard w/o suggestions to keyboard w/ suggestions.

Maybe from #6559 where toggleSuggestionBanner occurs on
prepareKeyboardSwitch and
setKeyboard

@mcdurdin
Copy link
Member

Noting for reference, so it isn't missed: in #9622, based on the video, the OSK temporarily goes to a desktop form-factor default when only sil_euro_latin is installed and it's reselected from the language picker.

@jahorton
Copy link
Contributor

@jahorton
Copy link
Contributor

jahorton commented Nov 16, 2023

Diving into something else we noticed: this block hasn't been changed since #1842, for version 14.0:

protected void onPause() {
super.onPause();
if (KMManager.InAppKeyboard != null) {
KMManager.InAppKeyboard.loadKeyboard();
}
if (KMManager.SystemKeyboard != null) {
KMManager.SystemKeyboard.loadKeyboard();
}
}

Before that, the loadKeyboard calls were wrapped in a conditional - they'd only activate if a keyboard download or update was triggered. (if (didUpdate) ...) This was back when keyboard updates were managed through the picker - in fact, this commit was part of said transition. git blame does point to me here; there's a strong chance that we can remove the calls and that I had simply been overcautious back then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants