-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ability to select non-accessible elements #31
Comments
should be possible with a mixture of current matchers I would look at a combination of native class + ancestor + button trait please confirm that you found a working matcher, share a gist with it and close this issue :) |
👍 |
you have a gist to share with how to match iOS back button? (for future generation benefit) |
oops forgot to share a gist! Here it is - |
I like the 2nd one better but I would prefer to avoid the label because: (1) can be localized (2) if you have a title on the previous screen does it have its title there instead of generic "Back"? What about replacing the How does this gist work when we have custom buttons in the nav bar? |
So: both works for the back button. BUT I suspect that these selectors could incorrectly match other navigation button (custom). Not sure though, we should probably try them against different variations of the nav bar. I can't however seem to find an explicit way to get to the Back button without an accessibility ID or label (except for the For custom button, you can use this (it does not match the Back button): |
hmm.. interesting. Maybe we can use |
For example, the navigator's
Back
UIAButton
The text was updated successfully, but these errors were encountered: