summaryrefslogtreecommitdiff
path: root/api/api_test.go
diff options
context:
space:
mode:
author Jordan Demeulenaere <jdemeulenaere@google.com> 2024-09-05 17:51:38 +0200
committer Jordan Demeulenaere <jdemeulenaere@google.com> 2024-10-23 10:31:19 +0200
commit8c2acf8c3a15b26f307fb8a0ba0b514161f447eb (patch)
treeb71d09ee9315434d29ab4b7e6e9c973440316fdb /api/api_test.go
parentea18b6d174ffbbded5d6755985a59cfdf3a30380 (diff)
Introduce sharedElement.elevateInContent (1/2)
This CL introduces a new elevateInContent parameter to draw an element above all other composables in its content (scene/overlay). It allows to prevent elements from being clipped by a parent (like a scrollable list) while still being drawn in the same content, therefore keeping a relatively similar zIndex in the whole SceneTransitionLayout compared to other scenes and overlays. The first version of this CL had `elevateInContent` be a simple `Boolean`. However, doing so would require us to instrument all scenes and overlays to always use Modifier.container(), and all elements to use Modifier.drawInContainer(), which are most of the time not necessary. Making elevateInContent by a `ContentKey?` allows to only compose these modifiers when necessary. Note that using this parameter can currently lead to some strange issues where text is not drawn (see b/374257277). I expect this to be fixed in the Compose libraries directly in the future. Bug: 373799480 Test: atest ElevateInContentScreenshotTest Flag: com.android.systemui.scene_container Change-Id: Ifa9e65ade0bc7bab01c80c0eb77c5424db13047f
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions