diff options
| author | Rob Carr <racarr@google.com> | 2020-03-06 15:33:31 -0800 |
|---|---|---|
| committer | Rob Carr <racarr@google.com> | 2020-03-09 10:47:54 -0700 |
| commit | 698b684fdd467c3e8d251cef9d4f9da0daa8195b (patch) | |
| tree | 8e0bd330390e9ae3f64c83c133f54351ec9fe16a /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 91b4f26c5b40292eac5a00e477eb747f1f859ba3 (diff) | |
WindowManager: Avoid reparenting BLAST Surface in reparentChildren
In cases where we are replacing the client surface transparently (e.g.
preserved surfaces), we call reparentChildren to move client added
Surfaces of the preserved Surface to the new Layer. However we are calling
this on the WSA layer, and so we end up reparenting the BLAST Surface
to the new layer. But since we always construct a new BLAST surface on the
WM side, we end up with 2! Rather than try and juggle about when we need
to or need not to construct a BLAST surface and reparenting them across
preservedSurfaces, it seemed either to just use the BLAST surface as the
root of the reparentChildren operation.
Bug: 150013915
Test: Enable BLAST, use split-screen
Change-Id: I1357200b41d183c2331b684ff636dd40a3b98168
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions