Bug #176

Keyboard does not pop up when selecting Find in Page

Added by Brian Toole almost 3 years ago. Updated over 2 years ago.

Next Release
Start date:
Due date:
% Done:


Estimated time:


Ideally, the keyboard will pop up when selecting Find in Page so we don't manually have to click on the search box again.


media-20170724.png (108 KB) media-20170724.png About -> Version Screenshot Brian Toole, 07/24/2017 01:03 PM



Updated by Soren Stoutner almost 3 years ago

  • Assignee set to Soren Stoutner
  • Priority changed from 2 to 3


On my devices, the keyboard does pop up automatically when selecting Find on Page. Can you give me more information to help me troubleshoot?

1. Do you always have the problem of the keyboard not showing when selecting Find on Page, or does it only happen in certain scenarios?
2. If it only happens in certain circumstances, please let me know what steps can replicate the problem.
3. Please send me a screenshot of About → Version. There may be something specific to your device that is causing the problem.


Updated by Brian Toole almost 3 years ago


It happens every time for me. I am using GBoard as my primary keyboard - I haven't tested with any others yet. Including my About -> Version screen.


Updated by Soren Stoutner almost 3 years ago

After looking at the code, I was reminded that to display the keyboard, I had to insert a delay of 200 ms after displaying the Find on Page bar. This is to work around a bug in Android.

My guess is that on some devices 200 ms is not sufficient. Please test out the following debug build where I have increased the delay to 300 ms. This debug build is of Privacy Browser Free (the ad supported version) which will allow you to install it alongside your current version without losing any of your settings.


Updated by Brian Toole almost 3 years ago

I tried the debug build, and it still didn't work. That being said, I do plan on getting a new phone later this year, and since its working as expected in your builds, I'd say close this bug unless others are reporting a similar issue. Since it seems like the fix to accommodate old devices would potentially negatively impact the experience in newer devices, catering to the older devices in this case isn't worthwhile.


Updated by Soren Stoutner almost 3 years ago

  • Status changed from New to Closed

Sounds good. Let me know if you still have problems after upgrading your device.


Updated by Soren Stoutner over 2 years ago

  • Priority changed from 3 to Next Release

Updated by Brian Toole over 2 years ago

Just an update on this one - once I upgraded to my Essential phone, I am no longer having this issue, so it seems like something that was just impacting some older devices.


Updated by Soren Stoutner over 2 years ago

Thanks for the update. If anyone else has this issue they should feel free to reopen the bug.

Also available in: Atom PDF