* changes:
[automerger] Add mStartState to determine if user swipes up from Home. am: 788c051493
Add mStartState to determine if user swipes up from Home.
Using the system logic for focus handling so that partially visible contents are
properly handled, eg in overview only hotseat is visible
This does changes the focus logic on workspace when both icons and widgets or different sizes
are present, we may consider reviving (parts of) this logic in the future
Bug: 80189843
Change-Id: I874e284e0a62b579c24d36db9b74da3de7a7e367
> Hiding the caret in fast overview state
> Hiding caret in task swipe down interaction
Bug: 79700605
Change-Id: I984d535bc75802501e8aeb13c8f37387f331e5bc
* changes:
[automerger] Reset the vertical progress when the discovery bounce is closed am: 0bd0244a73
Reset the vertical progress when the discovery bounce is closed
* changes:
[automerger] Skip processing fallback icons as they are already badged and have shadow am: fbf327f9ee
Skip processing fallback icons as they are already badged and have shadow
Keyboard navigation of AllAppsContainerView is broken in TOT; disabling
focusing there is necessary for Recents.
Bug: 72222505
Test: Manual
Change-Id: I85d544f7c8dbdaf12e49de51c6626bbc3dc32917
Since discovery bounce runs on absolute values, it can sometime leave the vertical progress
at an old value, if it is closed after the state change.
Also simplifying discovery bounce animation to use xml everytime.
Bug: 80099242
Change-Id: Iebc249dd02f474cbed85b695eeeb8c2bf60b935d
Add BackButtonAlphaHandler to set back button alpha, instead of setting
it from multiple places.
Also force back button alpha to be 1 if swipe up is disabled (b/80091187)
Change-Id: I49b63a0e6b033a3a947a847669a398f1b9ff0564
Normally when you hit back, we just close the floating view if there
is one. This makes less sense for DiscoveryBounce, since it doesn't
feel like a different state even though it's technically a floating
view. So in that case, don't consume the back press; let launcher
handle it to go to the previous state.
Bug: 80075741
Change-Id: I7270b61be70509cb2101400a12929478a5d082aa
* changes:
[automerger] Fixing reverted order of accessibility scrolling in Recents am: 0fc0713253
Fixing reverted order of accessibility scrolling in Recents
Now that batter saver mode doesn't get rid of animations in P, we
shouldn't use custom logic to prevent them either.
Also updated ATLEAST_P to use version code.
Bug: 79990054
Change-Id: If17cf369035c976f3d9d81f35432a045f1956ce5
Back button changes opacity when moving the shelf during swipe up
between home screen and overview. The alpha changes depending on the
progress of the swipe up animation. When going from app to home and vice
versa, the fade animation does not tie with the swipe up progress. The
fade animation also masks the back button drawable when ime visibility
changes.
Change-Id: I51e42930640ba711e81880b385bb722d7ee8ad33
Fixes: 74581837
Fixes: 76900236
Test: swipe up from home screen to overview
- Don't update the animation to go from 0 to 1; instead, update the
interpolator to clamp to the remaining progress (b/79773309)
- Fix NPE that can happen in a race between the atomic animation
ending and the non-atomic animation canceling/ending
Change-Id: I313251dc5cbd7b931b043fc3e840bb4ab368a790