4ccfdf7102c8fbf686d81ddd32b64bb7f7e40cab |
|
07-Dec-2017 |
Bryce Lee <brycelee@google.com> |
Re-add StackWindowControllerTests#testRemoveContainer_deferRemoval. Bug: 65379195 Test: atest FrameworksServicesTests:StackWindowControllerTests#testRemoveContainer_deferRemoval Change-Id: Icacc1483b7ba5b4f36dff448d7e6868d64b8020b
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|
2c8361e00245cc9dfa986ee38065776e591d9132 |
|
15-Sep-2017 |
Wale Ogunwale <ogunwale@google.com> |
Disable flaky test testRemoveContainer_deferRemoval Bug: 65379195 Test: bit FrameworksServicesTests:com.android.server.wm.StackWindowControllerTests Change-Id: Iee3fde155c083a4c4abe2f90529b20d172b5c328
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|
11cc516a925ac7fc814dbb0a79a7f0abfbfe1ce1 |
|
26-Apr-2017 |
Wale Ogunwale <ogunwale@google.com> |
Reduce use of static variables in window manager unit tests This was causing test cross-contamination since different test might expect different states from the variables. Bug: 37682538 Test: tons of it! Change-Id: Ie8a1ea400695b6346d7dfa3369b5c44bb467a33d
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|
51c1b670224fa1598644426b472d51346dd22f30 |
|
08-Apr-2017 |
Andrii Kulian <akulian@google.com> |
Fix activity move between displays 1. ActivityConfigCallback might not have been registered because DecorView was not yet attached to window and ViewRootImpl was not available. In this CL the callback is set as soon as a DecorView is attached to window. 2. When private display was removed from system, its stacks were moved to bottom in AM but moved to top in WM. 3. When reparenting stack visibility of activities should be updated before reparenting in WM, because otherwise WM will be resizing windows that should no longer visible and reporting it to clients. Bug: 34164473 Test: android.server.cts.ActivityManagerDisplayTests Test: #testOnMovedToDisplayCallback Test: #testContentDestroyOnDisplayRemoved Change-Id: I6ccc27d873d0d60d7650659fb25cbfcaaeb0fd07
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|
af691c0be7bbfea63e880dd717c51a38a0bc874a |
|
20-Mar-2017 |
Bryce Lee <brycelee@google.com> |
Clean up activity/stack associations. The stack currently holds a reference to resuming and pausing activities. These are usually cleaned up when the activity ends or the task is reparented. However, it is possible for an activity to lose its reference to its task in other areas (such as ActivityStarter), which can lead to the stack not being updated correctly. This changelist adds a method to the ActivityStack to disassociate the stack from an ActivityRecord. In addition to places where this is called when an activity ends, this method is invoked on the children of a task when the task is reparented. The task member variable of ActivityRecord is also now surrounded by a setter/getter, with the setter always invoking the dissociation logic on a previous stack. Test: bit FrameworksServicesTests:com.android.server.am.ActivityRecordTests Change-Id: Iffeccdb6f011958896271673946acfed28856f53 Fixes: 36387417
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|
367ff7fd5251790ad8dc086bd386be8cba1dda5c |
|
26-Jan-2017 |
Andrii Kulian <akulian@google.com> |
Fix shared dim layer not cleared when all users removed For secondary display, shared fullscreen dim layer user is the only stack that is present on the display. When this stack is removed the shared dim layer was not cleared. Because of that it was crashing when trying to obtain DisplayContent from it. Now when we're removing a dim layer user we check if we've removed the last one and clear shared fullscreen dim layer if needed. Bug: 34367817 Test: bit FrameworksServicesTests:com.android.server.wm.DimLayerControllerTests Change-Id: I415196a345c491eddd26a55370bb819ce6485151
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|
1666e317dc1a17e9435246ec6c8209dbb6ee3696 |
|
16-Dec-2016 |
Wale Ogunwale <ogunwale@google.com> |
Added StackWindowContainerController For linking ActivityStack in AMS to TaskStack window container in WMS. Change-Id: I8b9eaef49e62854d59b22d27f80f5935a5a4d7fc Bug: 30060889 Test: bit FrameworksServicesTests:com.android.server.wm.StackWindowContainerControllerTests Test: bit FrameworksServicesTests:com.android.server.wm.TaskWindowContainerControllerTests Test: Existing test pass and manual testing.
/frameworks/base/services/tests/servicestests/src/com/android/server/wm/StackWindowControllerTests.java
|