search

duckduckgo / Android

DuckDuckGo Android App
https://play.google.com/store/apps/details?id=com.duckduckgo.mobile.android
Apache License 2.0
3.78k stars 894 forks source link

AnySoftKeyboard ghosting when exiting apk to home screen #1080

Closed m1chj closed 2 years ago

m1chj commented 3 years ago

Describe the bug AnySoftKeyboard ghosting when leaving DDG with keyboard active at the moment of returning to home screen. This does not happen with Bromite or Iceraven. If I press back button, keyboard hides and then I go back to home screen, there's no ghosting.

How to Reproduce Steps to reproduce the behavior:

  1. Open DDG
  2. Wait for keyboard to show up
  3. Return to home screen
  4. See keyboard ghosting

Expected behavior See home screen right away without keyboard ghosting

Smartphone):

Clip recorded on P40 Pro

https://user-images.githubusercontent.com/45080190/106254655-410ce280-6219-11eb-86dd-8644157fa992.mp4

cmonfortep commented 3 years ago

Thanks for the feedback and for the recording too, really helpful.

That was fixed in our 5.70.0 release. If you are using f-droid, please check this issue (https://github.com/duckduckgo/Android/issues/1069)

m1chj commented 3 years ago

@cmonfortep this still happens with newest version 5.76.0 downloaded from GitHub

https://user-images.githubusercontent.com/45080190/106464869-88090b00-6499-11eb-9572-48e9278f7e63.mp4

cmonfortep commented 3 years ago

Thanks. I can't reproduce it on my device.

I will try to reproduce it using the system keyboard. Just to double-check, are you using the system keyboard or another keyboard app installed in your phone?

m1chj commented 3 years ago

I'm using AnySoftKeyboard 1.10.1109.6279 (in-app says 1.10-r3) from F-Droid. It's also the only keyboard I have installed since I ADB'd whatever it was as a system default.

m1chj commented 3 years ago

@cmonfortep it's the same with OpenBoard keyboard

cmonfortep commented 3 years ago

Thanks, I managed to reproduce the issue on my device using that keyboard.

ghost commented 3 years ago

I get this on 5.81.0 now, just with regular AOSP keyboard, except it stays up on the screen until you close it. It didn't happen before on older versions of the app.

cmonfortep commented 3 years ago

@Ammako we are trying to reproduce the scenario you mentioned, but the keyboard always goes away when sending the app to the background.

Would you mind giving us some more details (device, OS, current app version, ...)? also if you could share the steps to reproduce it (or record a video/gif), it will really helpful.

My steps are:

but the keyboard always hides, am I missing something?

ghost commented 3 years ago

I use a custom build of LineageOS 14.1 (7.1.2) on Nexus 5, it's not available online but I can upload it if needed. It comes with DuckDuckGo as a system app, and Bromite webview, in case that might be altering the behavior of the app (I wouldn't expect it to, though.)

Was on 5.81.0 but I'll let you know if I see it happen again on the current latest version. It only happens somewhat rarely, it doesn't happen just from switching the app away on an empty tab. I'll be browsing randomly and then I want to switch to another app to check an email or a message I just got, I use the recents app button to bring up my list of open apps and sometimes the keyboard goes away and then comes back and stays on, covering up most of the Recents screen.

cmonfortep commented 3 years ago

Thanks so much for your quick (and detailed) response. Let us know if you see the issue happening again and we will try to find the bug producing that unexpected issue with the keyboard.

cmonfortep commented 3 years ago

Sorry, wrong button when posting the comment :P

ghost commented 3 years ago

Just had it happen again. 5.86.2, I started up the app and browsed to openweathermap, searched for my city, got the forecast for the day. Then I opened Recents view to quickly close the browser, and keyboard decided it felt like popping up and staying up on Recents screen, even though it wasn't even up on the page in the first place.

Might be a different issue from the one in this thread, though. Should I move this to a separate issue?

Note it doesn't happen every time, so it might be difficult to reproduce, even for me.

cmonfortep commented 2 years ago

Closing as we haven't been able to reproduce the issue and we haven't received enough feedback to give it more priority in our backlog.