Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Setting z-order of the overlapping nodes at the same hierarchical level

Open
#700 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
android, rust
Domain
accessibility

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.

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.

    1. "Root Containter"
    • 1.1. "ListBox"
      • 1.1.1. "ListBox Item 1"
      • 1.1.2. "ListBox Item 2"
    • 1.2. "Containter"
      • 1.2.1. "Button"
Dominant language
Rust
Stars
1.5k
Forks
114
Avg merge
8h 25m
Merged PRs (30d)
28

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AccessKit/accesskit

All issues in AccessKit/accesskit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.