AccessKit / AccessKit/accesskit
Setting z-order of the overlapping nodes at the same hierarchical level
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 114
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 28
Description
There seems to be no way to explicitly specify z-order for the nodes.
With a node structure like this, where "ListBox" is popup and its bounding box overlaps button and its parent container. Android TalkBack explore by touch seems to randomly select button and overlapping list item.
-
- "Root Containter"
- 1.1. "ListBox"
- 1.1.1. "ListBox Item 1"
- 1.1.2. "ListBox Item 2"
- 1.2. "Containter"
- 1.2.1. "Button"
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the reported Root Container/ListBox/Container/Button hierarchy as the reproduction case, with Android TalkBack explore by touch as the observed behavior. The issue names no file, test, or entry point; done would require an agreed way to explicitly define z-order and verify deterministic selection for overlapping nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, rust
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100