Fixed
Status Update
Comments
jo...@google.com <jo...@google.com> #2
Can you provide the below requested information to better understand the issue:
Steps to reproduce
What steps are needed to reproduce this issue?
Please explain the reproduction steps in detail.
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot image to this issue.
Steps to reproduce
What steps are needed to reproduce this issue?
Please explain the reproduction steps in detail.
Expected output
Could you please explain the expected behavior.
Current output
Could you please explain the current behavior.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot image to this issue.
ph...@lu.ma <ph...@lu.ma> #3
Steps to reproduce:
1. Switch night mode to on/off;
2. Switch night mode to follow system.
Expected: Switch to the same night mode as the system currently uses.
Current: No changes at all.
1. Switch night mode to on/off;
2. Switch night mode to follow system.
Expected: Switch to the same night mode as the system currently uses.
Current: No changes at all.
jo...@google.com <jo...@google.com> #4
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ro...@osome.com <ro...@osome.com> #5
The fix for this went out in AppCompat v1.1.0-alpha03.
ap...@google.com <ap...@google.com> #6
The bug is still there with appcompat v1.7.0-alpha01
ap...@google.com <ap...@google.com> #7
Project: platform/frameworks/support
Branch: androidx-main
commit 00a9792162b32f60b64eeb5617fd46da749be323
Author: Jossi Wolf <jossiwolf@google.com>
Date: Fri May 12 17:08:38 2023
[M2] AnchoredDraggable Progress API
Improves AnchoredDraggable's progress API to match Swipeable's behavior. The progress is now exposed as the fraction of the current offset between the current (settled) anchor and the closest anchor in the swipe direction.
In contrast to the targetValue, the closestValue does not consider the thresholds.
Test: anchoredDraggable_closestValue, existing progress tests
Fixes: 270066861
Change-Id: I651e06cb34e914a63e13df851b27087d3bbb4257
M compose/material/material/src/androidAndroidTest/kotlin/androidx/compose/material/anchoredDraggable/AnchoredDraggableStateTest.kt
M compose/material/material/src/commonMain/kotlin/androidx/compose/material/AnchoredDraggable.kt
https://android-review.googlesource.com/2505862
Branch: androidx-main
commit 00a9792162b32f60b64eeb5617fd46da749be323
Author: Jossi Wolf <jossiwolf@google.com>
Date: Fri May 12 17:08:38 2023
[M2] AnchoredDraggable Progress API
Improves AnchoredDraggable's progress API to match Swipeable's behavior. The progress is now exposed as the fraction of the current offset between the current (settled) anchor and the closest anchor in the swipe direction.
In contrast to the targetValue, the closestValue does not consider the thresholds.
Test: anchoredDraggable_closestValue, existing progress tests
Fixes: 270066861
Change-Id: I651e06cb34e914a63e13df851b27087d3bbb4257
M compose/material/material/src/androidAndroidTest/kotlin/androidx/compose/material/anchoredDraggable/AnchoredDraggableStateTest.kt
M compose/material/material/src/commonMain/kotlin/androidx/compose/material/AnchoredDraggable.kt
[Deleted User] <[Deleted User]> #8
Hi! Is this gonna be in the next release of compose (1.5.0-beta02)?
ph...@gmail.com <ph...@gmail.com> #9
I also expected to see it in 1.5.0-beta02, but it's not there. It's only gonna be available in 1.6?
pr...@google.com <pr...@google.com> #10
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material:material:1.6.0-alpha01
androidx.compose.material:material-android:1.6.0-alpha01
ju...@google.com <ju...@google.com> #11
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.material:material:1.5.0-beta03
androidx.compose.material:material-android:1.5.0-beta03
na...@google.com <na...@google.com> #12
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.wear.compose:compose-material-core:1.2.0-rc01
androidx.wear.compose:compose-ui-tooling:1.2.0-rc01
Description
System
ModalBottomSheet
hides scrim quite early after you start swiping - I guess it indicates that sheet is gonna be dismissed at this point.I prefer to have a progressive scrim alpha - it drops smoothly to zero when the sheet is completely closed.
In Compose 1.3.0 I was using
ModalBottomSheetState.progress
to calculate scrim alpha depending on swipe progress.Looks like
SwipeableV2State
API is different fromSwipeableState
at this point. I guess that I can useModalBottomSheetState.currentValue
/ModalBottomSheetState.targetValue
instead ofSwipeableState.progress.from
/SwipeableState.progress.to
, but I still needSwipeableState.progress.friction
which seems likeSwipeableV2State.progress
now.Could you make it publicly available with
ModalBottomSheetState.progress
?