Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Android: only report text changes for the input-focused node (double speech)

Offen
  • Stimmt etwas nicht?
#844 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
android, rust
Bereich
accessibility, mobile-dev

Rechercherichtung

Start by reading AdapterChangeHandler::node_updated and the existing unit tests for text-change events. Check how input focus is represented and compare the event behavior with android.widget.TextView. Done means unfocused node text updates no longer emit TYPE_VIEW_TEXT_CHANGED, while updates to the focused edit field remain announced; verify that the content-change and live-region events still cover their cases.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Problem

The Android adapter sends TYPE_VIEW_TEXT_CHANGED for every node whose text changed. Screen readers echo that event whether or not the source node is focused, so an update to an unfocused node (for example a read-only log the app updates) is spoken on top of whatever the app announced itself, and the user hears it twice.

Proposed fix

Report the event only for the node with input focus, as android.widget.TextView does. Changes to other nodes are still covered by the window content-change event, and live regions by their own event. The change is a few lines in AdapterChangeHandler::node_updated plus a unit test.

Testing

Tested on a physical realme RMX5032 running Android 16 (API 36) with Google TalkBack 17.1.0 and with BackTalk, in an app using this adapter: the double speech is gone and typing in the focused edit field is still announced.

AI disclosure

I used an AI assistant (Claude) to help investigate and write this change. I reviewed the diff and ran the checks and the device testing myself.

I saw that AccessKit no longer accepts external pull requests (#832), so I'm opening an issue instead. If the plan looks reasonable, I'd be glad to send the PR as a member; I have the change ready and can share it however you prefer.

Vorherrschende Sprache
Rust
Sterne
1.5k
Forks
127
Ø Merge
16 Std. 45 Min.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AccessKit/accesskit

Alle Issues in AccessKit/accesskit

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.