New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 708407 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature



Sign in to add a comment

Omnibox Metrics - Android - Time From Tapping Omnibox Until Keyboard Appears

Project Member Reported by mpear...@chromium.org, Apr 5 2017

Issue description


Sometimes this takes a while.  I'm curious how long this typically takes.

 
Status: Available (was: Untriaged)
Cc: changwan@chromium.org
changwan@, does the Android keyboard API make it possible to calculate this?

thanks,
mark

Unfortunately, there is no standard way to do it. There is a long email thread between Android team and us. (also see b/37511008 for dismissal case)

Omnibox is an editor and has a passive role in editor-input method communication, and we cannot generally inquire the state of input method. It is possible to listen to layout size change - do the opposite of KeyboardHideHelper[1], but there are some problems I can think of:

1) Hardware keys are not considered.
2) Unlike hiding case, you need another hack to check where the showing animation ends.
3) Keyboard app may not be ready even when the animation finishes. For example, the user may be seeing a set up screen or a promotion / roll-in ads.

I thought listening to the first keystroke is enough. Let me know if you have a further question about this.


[1] https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/omnibox/KeyboardHideHelper.java

Status: WontFix (was: Available)
Thanks for the detailed response.  Listening for layout size changes sounds hacky and comes with caveats that you list.  I don't think this is important enough to add hacky code that'll give us iffy numbers.  Closing as WontFix.

Sign in to add a comment