Fixed
Status Update
No update yet.
Comments
je...@google.com
Hi. Thanks for reporting this. Fixed in alpha-04
ch...@gmail.com
Project: platform/frameworks/support
Branch: androidx-main
commit e782987543a9f8ccd485e970ddc74564b24378db
Author: Vighnesh Raut <vighnesh.raut13@gmail.com>
Date: Mon Jan 02 15:27:40 2023
fix: tab row crashes when only 1 tab is added
Bug:
Test: Added unit test
Change-Id: I6381dbac304fc1d69d3708c6655f8b595668e93f
M tv/tv-material/src/androidTest/java/androidx/tv/material/TabRowTest.kt
M tv/tv-material/src/main/java/androidx/tv/material/TabRow.kt
https://android-review.googlesource.com/2373449
Branch: androidx-main
commit e782987543a9f8ccd485e970ddc74564b24378db
Author: Vighnesh Raut <vighnesh.raut13@gmail.com>
Date: Mon Jan 02 15:27:40 2023
fix: tab row crashes when only 1 tab is added
Bug:
Test: Added unit test
Change-Id: I6381dbac304fc1d69d3708c6655f8b595668e93f
M tv/tv-material/src/androidTest/java/androidx/tv/material/TabRowTest.kt
M tv/tv-material/src/main/java/androidx/tv/material/TabRow.kt
je...@google.com
deleted
je...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.tv:tv-material:1.0.0-alpha04
ap...@google.com
Project: platform/frameworks/support
Branch: androidx-main
commit ebf2e69f48e922f8abced7626b587bfc7745da01
Author: Jelle Fresen <jellefresen@google.com>
Date: Thu Sep 02 15:37:36 2021
Generate better swipes with velocity
This uses a new algorithm to derive a function for the path of the swipe
which results in much looser constraints. When a function can't be
created because the parameters are too strict, it will give suggestions
for adjustments in the parameters so that it becomes possible to
generate a swipe that ends with a given velocity.
Bug: 182477143
Test: ./gradlew compose:ui:ui-test:cC
Relnote: "Improved `TouchInjectionScope.swipeWithVelocity`. It now
accepts a wider range of input variables and will suggest changes to the
input if a swipe can't be created"
Change-Id: I40fbe57b6f28689bc2597b2e64ae0ef28158e593
M compose/ui/ui-test/src/androidAndroidTest/kotlin/androidx/compose/ui/test/injectionscope/touch/SwipeWithVelocityTest.kt
A compose/ui/ui-test/src/androidAndroidTest/kotlin/androidx/compose/ui/test/injectionscope/touch/VelocityPathFinderTest.kt
M compose/ui/ui-test/src/androidAndroidTest/kotlin/androidx/compose/ui/test/util/Truth.kt
M compose/ui/ui-test/src/commonMain/kotlin/androidx/compose/ui/test/TouchInjectionScope.kt
A compose/ui/ui-test/src/commonMain/kotlin/androidx/compose/ui/test/VelocityPathFinder.kt
https://android-review.googlesource.com/1823303
Branch: androidx-main
commit ebf2e69f48e922f8abced7626b587bfc7745da01
Author: Jelle Fresen <jellefresen@google.com>
Date: Thu Sep 02 15:37:36 2021
Generate better swipes with velocity
This uses a new algorithm to derive a function for the path of the swipe
which results in much looser constraints. When a function can't be
created because the parameters are too strict, it will give suggestions
for adjustments in the parameters so that it becomes possible to
generate a swipe that ends with a given velocity.
Bug: 182477143
Test: ./gradlew compose:ui:ui-test:cC
Relnote: "Improved `TouchInjectionScope.swipeWithVelocity`. It now
accepts a wider range of input variables and will suggest changes to the
input if a swipe can't be created"
Change-Id: I40fbe57b6f28689bc2597b2e64ae0ef28158e593
M compose/ui/ui-test/src/androidAndroidTest/kotlin/androidx/compose/ui/test/injectionscope/touch/SwipeWithVelocityTest.kt
A compose/ui/ui-test/src/androidAndroidTest/kotlin/androidx/compose/ui/test/injectionscope/touch/VelocityPathFinderTest.kt
M compose/ui/ui-test/src/androidAndroidTest/kotlin/androidx/compose/ui/test/util/Truth.kt
M compose/ui/ui-test/src/commonMain/kotlin/androidx/compose/ui/test/TouchInjectionScope.kt
A compose/ui/ui-test/src/commonMain/kotlin/androidx/compose/ui/test/VelocityPathFinder.kt
Description
I'm using
swipeWithVelocity()to test a scrolling layout, but I've found it difficult to find the magic combination of distance, duration and velocity to make it work.I consistently see the following error in tests:
While I can find some values which work for 1 device, it may not work for all devices, due to different sizes.