Verified
Status Update
Comments
mo...@google.com <mo...@google.com>
gr...@google.com <gr...@google.com> #2
Hi. Thanks for reporting this. Fixed in alpha-04
gr...@google.com <gr...@google.com> #3
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: b/264018028
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
ap...@google.com <ap...@google.com> #4
deleted
gr...@google.com <gr...@google.com> #5
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 <ap...@google.com> #8
Project: platform/frameworks/support
Branch: androidx-main
Author: Grant Toepfer <
Link:
Stabilize invisibleToUser
Expand for full commit details
Stabilize `invisibleToUser`
A 1.7 cherry-pick (aosp/3341487) to fix b/376479686 calls `invisibleToUser` from the foundation module, but it cannot depend on `invisibleToUser` if it is still experimental, so experimental was removed from `invisibleToUser` in 1.7 (via aosp/3387946). This change removes experimental from `invisibleToUser` in 1.8+ so that it matches the change in 1.7 for binary compatibility.
Leaving relnote blank since `invisibleToUser` is still deprecated in 1.8+
Relnote: N/A
Bug: b/376479686
Test: N/A
Change-Id: I40cdd6a3d335011e890761560a5a3416aa579991
Files:
- M
compose/ui/ui/api/current.txt
- M
compose/ui/ui/api/restricted_current.txt
- M
compose/ui/ui/src/androidMain/kotlin/androidx/compose/ui/platform/SemanticsUtils.android.kt
- M
compose/ui/ui/src/commonMain/kotlin/androidx/compose/ui/semantics/SemanticsProperties.kt
Hash: 211cbf6550baa068eb56bf80d767c5ef1e882674
Date: Mon Dec 02 16:33:49 2024
gr...@google.com <gr...@google.com>
bu...@google.com <bu...@google.com> #9
Hi. I've received your bug and will wait until 2024-12-15 16:42 -0800 PST and then assign the bug to grantapher@google.com.
bu...@google.com <bu...@google.com> #11
Hi. I've received your bug and will wait until 2024-12-15 16:43 -0800 PST and then assign the bug to grantapher@google.com.
gr...@google.com <gr...@google.com> #12
Should be fixed in compose foundation 1.7.6
. Reporter, please verify your use case is working.
si...@gmail.com <si...@gmail.com> #13
Can confirm the fix is working in 1.7.6
Description
Jetpack Compose version: 1.7.5
Jetpack Compose component(s) used: foundation
Steps to Reproduce or Code Sample to Reproduce:
TalkBack TreeDebug logs:
Version 1.6.8 (BOM 2024.08.00)
Notice last line - "Important warning" is present
Version 1.7.5 (BOM 2024.10.01)
There "Important warning" is missing
Version 1.8.0-alpha05 (BOM-alpha 2024.10.01)
There "Important warning" is back again
It seems like this regression was added in Icd0becab6818712ab7fa6f3abe83f441a841af5e and fixed in I531e7bad97cda327974696686357a9e56430a6a6 (see TextAnnotatedStringNode.shouldClearDescendantSemantics). Although it is fixed in 1.8-alpha, version 1.7 is broken, preventing our app from updating.