so far I have a couple of questions about the mocks for lock screen:
1. the notification has a "Learn more" link - what is clicking the link expected to do, provided that we can't open a browser window on lock screen?
2. the user might have a pin enabled on lock screen, in which case there might space for us to show the notification under the auth input
1. On sign-in screen, "Learn more" opens the article in guest mode. On lockscreen, let's hide "Learn more".
2. Error dialog shows above the PIN pad as in attached screenshot. This should be reusing the same error dialog UI as other sign-in/lockscreen errors.
Deleted:
Screenshot 2018-02-14 at 2.06.30 PM.png
534 KB
I see hammerd exposes dbus API with signals about pairing/firmware update state.
Are there plans to add API for Chrome to query the base state? I'm worried about Chrome missing the signals from hammerd - e.g. if a signal is sent before Chrome starts, or while Chrome session is restarting/shutting down (for example on sign-out, or due to a crash).
Comment 1 by mnissler@chromium.org
, Dec 20 2017Owner: r...@chromium.org