One possible solution is to let goofy invoke chrome_openurl when some special event is found, and change restarting.html to use that for loading new page.

 Issue 766568  has been merged into this issue.

ToT is broken and this is indeed a P0 issue. We need some immediate solution, or we'll have to change the init url from extension page to http://localhost:4012, with the issue that focus can't be set.

Create a chrome app with a webview can get focus correctly.

Not sure if this will introduce new bugs..

pihsun has a one line change. let's use it first :)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/factory/+/3a0644b1c46979b8dea320efd5035231a1728da6

commit 3a0644b1c46979b8dea320efd5035231a1728da6
Author: Peter Shih <pihsun@chromium.org>
Date: Wed Sep 20 18:30:22 2017

Fix the extension is blocked problem on initial UI.

Chrome browser can't load initial URL in extension on ToT, and would
show a "<factory_test_extension_id> is blocked" page.

To work around this and have correct focus for first page, we create a
data URL that would connect to remote debugger, open a new tab to
factory UI, and close itself.

BUG= chromium:766570 ,b:65811583
TEST=make test
TEST=manually on DUT, reboot and check the focus is correct by
     ctrl-alt-0.

Change-Id: Ifc7435b74622883c0be7aa4ac1067b0844e38ce0
Reviewed-on: https://chromium-review.googlesource.com/674468
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Commit-Ready: Chia-Hsiu Chang <chia-hsiu.chang@quantatw.com>
Tested-by: Pi-Hsun Shih <pihsun@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>

[modify] https://crrev.com/3a0644b1c46979b8dea320efd5035231a1728da6/init/goofy.d/monolithic/chrome_dev.conf