Flaky JS error in setBatteryPercent at oobe/login.js |
|||||
Issue description
Chrome Version: ToT
OS: Chrome OS
What steps will reproduce the problem?
(1) Go to Chrome OS login screen.
What happens instead?
Everything seems to work as normal, but the ui.LATEST log sometimes contains an error:
[ERROR:CONSOLE(8544)] "TypeError: Cannot read property 'apply' of undefined
at Object.api.(anonymous function) [as setBatteryPercent] (chrome://oobe/login.js:415:42)
at <anonymous>:1:33", source: chrome://oobe/login.js (8544)
,
Apr 13 2017
,
Apr 13 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f925a21a93ff3fb173fcd9bca9146ad3b002083a commit f925a21a93ff3fb173fcd9bca9146ad3b002083a Author: Xiyuan Xia <xiyuan@chromium.org> Date: Thu Apr 13 18:28:16 2017 Start power observing when migration screen initialized Migration screen handler ctor is called during OobeUI creation in browser process and power callback could call JS too early before the renderer side finishes initialization. Defer the observing start to Initialize that is called when page js is ready. BUG= 711269 Change-Id: I866fd33ca68341fb646f4612a430b5eb1921e6f3 Reviewed-on: https://chromium-review.googlesource.com/477113 Reviewed-by: Naoki Fukino <fukino@chromium.org> Commit-Queue: Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#464476} [modify] https://crrev.com/f925a21a93ff3fb173fcd9bca9146ad3b002083a/chrome/browser/ui/webui/chromeos/login/encryption_migration_screen_handler.cc
,
Apr 13 2017
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xiy...@chromium.org
, Apr 13 2017Owner: xiy...@chromium.org
Status: Assigned (was: Untriaged)