mirror of
https://github.com/bitwarden/android.git
synced 2026-10-22 02:53:19 -05:00
ifernandezdiazandClaude Opus 4.8
c7fd0b1f88
The AddEditBlockedUriDialog used a raw Compose Dialog whose root never
enabled testTagsAsResourceId, so the "BlockedUriEntry" testTag was not
exported as a resource-id in the accessibility node tree. This made the
field invisible to UIAutomator/Appium (and any resource-id-based
automation), even though Compose UI tests using onNodeWithTag still passed.
Add Modifier.semantics { testTagsAsResourceId = true } to the dialog's
root Column, matching the pattern used by BitwardenScaffold and the other
Bitwarden dialog wrappers (e.g. BitwardenTwoButtonDialog). Dialogs render
in a separate composition window, so the scaffold's flag does not reach
them and each dialog must enable it on its own root.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>