OSDN Git Service

Freeze task bounds when relaunching
authorJorim Jaggi <jjaggi@google.com>
Tue, 22 Dec 2015 15:29:16 +0000 (16:29 +0100)
committerJorim Jaggi <jjaggi@google.com>
Tue, 5 Jan 2016 12:49:23 +0000 (13:49 +0100)
commit0429f3522bca5bb86378dd3f013f995484ddbed6
tree9687b4e71d961b0975873d031132b295bd0c2b79
parentfe89d122e5b6b129b25d5d5316f690bd4ab93fbb
Freeze task bounds when relaunching

To make sure that task is only laid out with the size
that matches the current configuration, we have to "freeze"
the task bounds when we send a configuration change. Without this
change, it could happen that the app already laid out with the new
task bounds, but still had the old configuration, leading to
wrong layouts.

Bug: 26311778
Bug: 25015474

Change-Id: I8d3a3fdf3735f446a4affbbdb4986dafc97623a5
services/core/java/com/android/server/am/ActivityStackSupervisor.java
services/core/java/com/android/server/wm/AppWindowToken.java
services/core/java/com/android/server/wm/Task.java
services/core/java/com/android/server/wm/TaskStack.java
services/core/java/com/android/server/wm/WindowManagerService.java
services/core/java/com/android/server/wm/WindowState.java