VirtualKeyboard.InitLatency.FirstLoad is not exported. |
||||||
Issue descriptionChrome Version: 58.0.3209.39 OS: 9334.23.0 kevin What steps will reproduce the problem? (1) Login to Chrome OS (2) Open virtual keyboard by tapping omnibox of Chrome on tablet mode (3) Open chrome://histograms What is the expected result? The metric VirtualKeyboard.InitLatency.FirstLoad should be exported What happens instead? It is not. Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
May 8 2017
,
May 8 2017
,
May 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2f2a04f5e41f313d9170f6263c12f780024093f4 commit 2f2a04f5e41f313d9170f6263c12f780024093f4 Author: yhanada <yhanada@chromium.org> Date: Tue May 16 01:47:52 2017 Fix 'VirtualKeyboard.InitLatency.FirstLoad' metric to be recorded for any keyboards. This metric was recorded when chrome.virtualKeyboardPrivate.keyboardLoaded API, but some keyboards don't call this API after loading is finished. In order to record this metric for any keyboard, this CL changes to call MarkKeyboardLoadFinished() after showing animation is finished. TEST=Confirm that the metrics is recorded in chrome://histograms. BUG=708362, 705926 Review-Url: https://codereview.chromium.org/2864413003 Cr-Commit-Position: refs/heads/master@{#471978} [modify] https://crrev.com/2f2a04f5e41f313d9170f6263c12f780024093f4/chrome/browser/extensions/api/virtual_keyboard_private/chrome_virtual_keyboard_delegate.cc [modify] https://crrev.com/2f2a04f5e41f313d9170f6263c12f780024093f4/ui/keyboard/keyboard_controller.cc [modify] https://crrev.com/2f2a04f5e41f313d9170f6263c12f780024093f4/ui/keyboard/keyboard_util.cc
,
May 16 2017
,
May 17 2017
,
Jul 6 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by oka@chromium.org
, Mar 28 2017