am: e1b5670
* commit 'e1b56701fd219227adae615fe81f03d5db4ae433':
Remove links to createAndInitializeUser() and createUser()
Resolve merge conflicts of a5060ee to nyc-dev
Change-Id: I8cf43f9ad491c6f23eb5fe0051293267ab2d03bf
am: ae3539f
* commit 'ae3539f055b01cda145ed0f8f826c60865964648':
Respect WRAP_CONTENT when resolving drop down position.
Change-Id: I5c4752f51747d08bfdfb4530e6ed3e32b99dd90c
am: 254f1b8
* commit '254f1b8a43480749b7061129289d34bc15d345a5':
Remove links to createAndInitializeUser() and createUser()
Resolve merge conflicts of a5060ee to nyc-dev
Change-Id: I32a3081af9ca5533785c90b7239ffd5b5e69d5bf
am: bf2a2fa
* commit 'bf2a2fafaf7659352dbc36de507e52dceceecaad':
Respect WRAP_CONTENT when resolving drop down position.
Change-Id: I82ab0dcef53f34ba5275826e47a724842bd6cdd8
am: 7a1ae0b
* commit '7a1ae0bce2b86ee881ed0fe0bc25cdaa54922c16':
Expose additional fields needed by PrintRecommendationService GTS test and move files into properly named directory.
Change-Id: Iaefe74d98b308d9ed676b47dfcc96222ec476ab8
am: a1a1aa3
* commit 'a1a1aa3c682215f0ac7251c43f77985b9aced2a2':
Expose additional fields needed by PrintRecommendationService GTS test and move files into properly named directory.
Change-Id: I6a177370c3fdcf0d81eedc3bc383f389f058b06a
am: 512ab59
* commit '512ab599fc903da21b67c0c4d01ce9ffb8e6d68f':
Kill foreground apps when turning off work
Change-Id: I83e0e9792225416c6a0c9de4a8201dcb2e37666f
am: 49425d6
* commit '49425d612cee3864a316e9ecb6ec3faeae519b1e':
Kill foreground apps when turning off work
Change-Id: Ie8ea1ec98232437623c83f7d32c1f05c47580b35
We recently added the width/height <0 check to prevent
passing unresolved widths in to tryFitVertical or
tryFitHorizontal and produce strange behaviors. This made
more sense than the code before it but still not that much
sense. We need to treat MATCH_PARENT and WRAP_CONTENT differently
as the documentation suggests.
Bug: 28267951
Change-Id: I6f2f248c8d1f63d31bdd75c24f7250c28381c712
am: 465ff1f
* commit '465ff1f9e61953eb57ab2fe3ff3405abebc79628':
Force windows to be scalable during pinned animation.
Change-Id: I49a8373aad59842e28847f36511e662c7087d4b3
am: 4e9a9df
* commit '4e9a9dfb67ebc48028b1613a03144101d94f7d92':
Force windows to be scalable during pinned animation.
Change-Id: I772d120442ed82c55c71fbf5ce841735d7a14cc5
- Make sure to draw navigation bar/status bar background before the
main render node. This is to avoid any flickering when entering
resizing mode, so you rather overdraw than underdraw.
- Draw the first frame from the main thread directly to increase
chance that all drawing commands are processing within a single
frame.
Bug: 27864358
Bug: 28003586
Change-Id: I033f57cdbcb2c16ea93134c041095a415d5c25b4
am: 67288c5
* commit '67288c5b6f05e18e85dd9a520f273d311952276f':
Consolidate the HealthStats UI to only use milliseconds.
Change-Id: I8ea14a4502f124daee32c0ef92130200431f04e7
am: 6ee19e4
* commit '6ee19e49346eea5d096933611586ab2b9d86e86d':
Consolidate the HealthStats UI to only use milliseconds.
Change-Id: Idf18eb11cff73c174072b4ab831bc35b5cb467de
am: 4c4afed
* commit '4c4afedfc5134558c1f674c1fc8f41260e07bdeb':
Consolidate the HealthStats UI to only use milliseconds.
Change-Id: I875b82483386bce75b35304970b6020d1da2ed5d
We resize windows at the beginning of the pinned stack
animation when animating to a larger size, and so for some
duration a resize will be pending. We need to force the window
out of SCALING_MODE_FREEZE so we can animate during this period.
Bug: 27891386
Change-Id: I5cff599ed67f2c179e938662b6f0d99bd790aaba
