cua-driver (Linux): consider the X11 root AT_SPI_BUS property when finding the accessibility bus
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- linux, rust
- Domain
- accessibility, testing
Research direction
Find the Linux cua-driver code that resolves the accessibility bus and the existing private-bus tests. Read the bus lookup path and test setup first. Add coverage for an unset AT_SPI_BUS_ADDRESS with a reachable X11 root AT_SPI_BUS property, and confirm the driver joins that bus before falling back to GetAddress.
Written by the indexing model from the issue text.
Description
Follow-up to #7943 (refs #4874).
libatspi resolves the accessibility bus in this order: the AT_SPI_BUS_ADDRESS environment variable, then the X11 root-window AT_SPI_BUS property, then org.a11y.Bus.GetAddress. After #7943 the driver tries the environment variable and then GetAddress, but still skips the root-window property.
In a normal session the property carries the same address GetAddress returns, so it was left out of #7943. It should be added if a #4874 reporter's session turns out to set only the property (no AT_SPI_BUS_ADDRESS, and a property that differs from GetAddress).
Done when
- On X11, when
AT_SPI_BUS_ADDRESSis unset and the rootAT_SPI_BUSproperty is set and reachable, the driver joins that bus before falling back toGetAddress. - A private-bus test covers the property path.
- Dominant language
- Rust
- Stars
- 32.3k
- Forks
- 2.4k
- Avg merge
- 4h 47m
- Merged PRs (30d)
- 711
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from trycua/cua
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 5 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
marketing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
5 advisory ignore entries no longer match anything in `Cargo.lock`Possibly taken @zyl71 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 75/100