Local NTP: Figure out loading sequence and animations |
||||||||||
Issue descriptionThe local NTP loads a bunch of stuff asynchronously: - Tiles (metadata, then thumbnail images) - Theme (background color sync, actual theme async) - Doodle - OneGoogleBar There's currently no well-defined order. Some of these animate, some don't. There are also dependencies, e.g. we only want to show a Doodle if there is a white background. We need to figure out the proper order and "motion choreography" for everything.
,
Jan 11 2018
Issue 736664 has been merged into this issue.
,
Aug 8
,
Aug 9
,
Oct 9
,
Oct 9
,
Oct 10
,
Nov 15
Finally getting to this. I've made animations of what I think will work best for our 2 main background transitions: 1. Default white -> Background image https://drive.google.com/open?id=14gwQ5aOcdeghlxG1Vj5uHvUiCdTAohbi 2. Background image -> New Background image https://drive.google.com/open?id=15QlGahh47v_qDXv-d46wz_6b6yqMh6th I've added a transition spec to show the timing and layering of the UI. Also, just a couple notes based on our last meeting on the coordination of elements here. – Show shortcut, header, and fakebox as soon as possible/immediately – Scrim/gradient is always present (does not transition) when a background is set – Hold at selection dialog w/ spinner in button until new image is fetched...then start 0.8 sec transition.
,
Nov 15
,
Nov 15
,
Nov 28
The NextAction date has arrived: 2018-11-28
,
Dec 28
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by fi...@chromium.org
, Oct 2 2017