-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[RNMobile] Improve AztecWrapper RN talkback support #25384
[RNMobile] Improve AztecWrapper RN talkback support #25384
Conversation
@cameronvoell @mchowning could you please add the relevant labels here for me 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and working well. LGTM!
I also ran through the test steps for wordpress-mobile/gutenberg-mobile#1076 (which is the PR that added the aztecText.setFocusable(false)
line in order to check for regressions, and I did not observe any problems. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please ignore this PR review (it's just for testing GitHub Slack PR notifications)
@guarani could you merge this for me. Thanks 🙏 |
Done @jd-alexander ✅ |
Fixes wordpress-mobile/gutenberg-mobile#918
Aztec Android PR wordpress-mobile/AztecEditor-Android#927
Gutenberg Mobile PR wordpress-mobile/gutenberg-mobile#2630
Description
Currently the RichText will focus automatically without needing double tapping. This was taking place due to the
AccessibilityDelegate
inAztec
requesting focus on hover, so that behavior was removed. This PR, resolves this by utilizing the mentioned fix within Aztec along with enabling theRichText
component via theReactAztecManager
so that thedouble-tap to activate
behavior becomes active.Testing
This was first tested in Aztec by ensuring that the
AztecText
view no longer auto focuses on hover. The commit hash of the Aztec PR was then utilized within Gutenberg to verify that the editor would no longer perform this auto-focusing.For further testing here are the instructions.
RichText
such as a paragraph block.Screenshots
Video Example
Concerns
The only change made in this PR I was wondering about is the removal of
setFocusable(false)
I tried to utilize git blame to figure out why this was added in the first place but I wasn't able to find a commit with enough details, hence I am pointing it out here.Update this was being discussed here as well. I will look into it more.
Checklist:
Review