Skip to content

Add mode selector - #751

Merged
thestinger merged 1 commit into
GrapheneOS:compose-prototypefrom
m4pl:task/736-mode-selector-composable
Oct 4, 2026
Merged

thestinger merged 1 commit into
GrapheneOS:compose-prototypefrom
m4pl:task/736-mode-selector-composable

Conversation

@m4pl

@m4pl m4pl commented Oct 3, 2026

Copy link
Copy Markdown
image

You can check it here - ModeSelectorSample.kt

Closes #736

@m4pl
m4pl force-pushed the task/736-mode-selector-composable branch 2 times, most recently from 3b93575 to fcc898a Compare October 3, 2026 13:29
@m4pl
m4pl requested review from RankoR and sdsantos October 3, 2026 13:29
@m4pl
m4pl marked this pull request as ready for review October 3, 2026 13:29
@m4pl
m4pl force-pushed the task/736-mode-selector-composable branch from fcc898a to e245a5a Compare October 4, 2026 20:51
@thestinger
thestinger merged commit 4bd4559 into GrapheneOS:compose-prototype Oct 4, 2026
2 checks passed
columnIndex = index,
columnSpan = 1,
)
this.customActions = customActions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not familiar with accessibility in Tabs. But it feels a bit weird that each individual tab has custom actions to select all other tabs except the focused tab, including the already selected tab. I know that the main action selects it.

I would expect either:
a) Just custom actions on the TabGroup level, that would let me select an individual tab.
b) That individual tab custom actions include the tab itself if it's not selected, and not include the already selected tab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants