diff options
| author | Andrii Kulian <akulian@google.com> | 2019-01-24 17:04:36 -0800 |
|---|---|---|
| committer | Andrii Kulian <akulian@google.com> | 2019-01-24 18:37:58 -0800 |
| commit | 996df0dbca73e09f9fbb793c0f90dc3d0b4892da (patch) | |
| tree | 3095faa71bf4241d60894eb7a3379ddf96d1576b /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 6b321517480924e5e977e0ef2437457f384280ab (diff) | |
Don't make active activities that are launched behind
Activities that are being launched behind are not intended to be
presented to the user, so they should not be made active (resumed
or paused) based just on their visibility and position.
One example is home/recents activity during transition from an
app to home after home button press with QuickStep enabled - the
home stack is made visible for the duration of the transition,
but it's still behind a fullscreen app stack and should not be
resumed immediately.
Bug: 123166999
Bug: 117135575
Test: ActivityManagerActivityVisibilityTests#testGoingHomeMultipleTimes
Test: ActivityManagerActivityVisibilityTests#testPressingHomeButtonMultipleTimes
Test: ActivityManagerActivityVisibilityTests#testPressingHomeButtonMultipleTimesQuick
Test: Manually switch between home and app with QuickStep enabled
Change-Id: I1106cf3da923e60d02b84d5fe4a552865113afc8
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions