diff options
| author | chaviw <chaviw@google.com> | 2019-01-18 15:49:56 -0800 |
|---|---|---|
| committer | chaviw <chaviw@google.com> | 2019-01-22 10:45:46 -0800 |
| commit | b4fa081ca7b9f2828869164b4df57a79bbd5398c (patch) | |
| tree | c31471a26784d47967fabe9c1f1e1480853ae1e3 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 793f1a793c2b9cd8f7356b83b8a2e5fd8d444e9b (diff) | |
Use Transaction reparent to null instead of destroy for SC in DragState
When creating a drag surface for drag and drop, the system server is
responsible for destroying the surface when no longer needed. However,
the SurfaceControl was created on the client side, so when the server
calls destroy, it's not allowed since only the process that created the
surface can do it.
Instead use the Transaction reparent to null to destroy the SurfaceControl.
Change-Id: Ie1f0c230046e9928cd4b12ff7a908aad70166d64
Fixes: 122798367
Test: Drag and drop no longer keeps shadow surface on screen
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions