desktopui_ScreenLocker currently has hard-coded assumptions that the lock screen is written in JavaScript/HTML and makes calls directly into it.
We should replace these JS calls with new APIs either in autotestPrivate, or possibly via a new mojo interface that autotest can access.
On further thought, we should instead try to submit keyboard events so that the autotest is completely independent of UI and does not rely on autotestPrivate.
Comment 1 by jdufault@chromium.org
, Nov 8 2017Owner: xiaoyinh@chromium.org
Status: Assigned (was: Untriaged)