Rene Win
05/19/2022, 9:01 AM@Composable
fun Home(navController: NavController) {
Column(
modifier = Modifier.testTag("hometag")
) {
Text("home1")
Text("home2")
Button(onClick = {
navController.navigate("detail",
)
}) {
Text("NEXT")
}
}
}
@Composable
fun Detail(navController: NavController) {
Column(
modifier = Modifier
.testTag("detailTag")
) {
Text("detail1")
Text("detail2")
Text("detail3")
}
}
Is there something I can do against that behaviour? Thanks in advance!Jelle Fresen [G]
05/19/2022, 1:52 PMRene Win
05/20/2022, 5:26 AMZach Klippenstein (he/him) [MOD]
05/24/2022, 4:11 PMRene Win
05/25/2022, 6:42 AMZach Klippenstein (he/him) [MOD]
05/25/2022, 3:08 PMRene Win
05/30/2022, 3:54 AMZach Klippenstein (he/him) [MOD]
05/30/2022, 5:50 PMRene Win
05/31/2022, 4:04 AM@Composable
fun Home(navController: NavController) {
Column(
modifier = Modifier
.testTag("hometag")
) {
Text("home1")
Text("home2")
Button(onClick = {
navController.navigate(
"detail"
)
}) {
Text("NEXT")
}
}
}
@Composable
fun Detail() {
Column(
modifier = Modifier
.testTag("detailTag")
) {
Text("detail1")
Text("detail2")
Button(onClick = { /*TODO*/ }) {
Text("detail3")
}
}
}
then the screen reader is again on the wrong element. (even with compose 1.2.0-beta02)
the only thing i changed is wrapping the Text("detail3") in a button, so the structure is the same as in the screen before.