-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[iOS] Inherit AccessibilityTraits for views wrapped inside a WrapperView #27088
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
base: main
Are you sure you want to change the base?
[iOS] Inherit AccessibilityTraits for views wrapped inside a WrapperView #27088
Conversation
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
This comment was marked as off-topic.
This comment was marked as off-topic.
a3c0ac1
to
becc282
Compare
Azure Pipelines successfully started running 3 pipeline(s). |
This comment was marked as outdated.
This comment was marked as outdated.
becc282
to
9abae1c
Compare
Azure Pipelines successfully started running 3 pipeline(s). |
9abae1c
to
782b745
Compare
Can we add a test to inspect if the button has the correct Traits? |
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.
LGTM, just, could include a device test verifying the AccessibilityTraits
?
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.
I was working on something similar with the TGR on labels. Let me confirm some things before we merge this one
I'll try to get the UITests uploaded tomorrow |
@tj-devel709 the test looks awesome |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
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.
I think we might want to fix this issue higher up.
My guess is that we have differing places where we are applying accessibility properties to the WrapperView vs the PlatformView
So, I'm wondering if we just need to fix all those places to pick one.
For example, in the GesturePlatformManager.ios.cs we are applying all those values to the wrapper view but should we be applying them to the wrapped view?
Should we be applying these values to both?
I think it's risky putting this behavior purely in the WrapperView and will just lead to more missed scenarios down the road
Issues Fixed
Fixes #26990