Skip to content
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

Don't mirror isAccessibilityElement on _ASTableViewCell #2062

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bdolman
Copy link
Contributor

@bdolman bdolman commented Apr 18, 2022

This is a partial revert of #1941

The change in #1941 has caused some issues for us and others (see #1997). If I set myNode.isAccessibilityElement = true, then what ends up happening is that the table cell wrapper view (_ASTableViewCell) also has isAccessibilityElement = true. But then when iOS goes through the hierarchy it identifies the table cell wrapper view as the target and attempts to use that accessibilityLabel, which doesn't exist (because it's actually on the nested node view). So our node's label is never used.

I'm not sure why setting isAccessibilityElement in _ASTableViewCell was necessary in #1941 in order to make a node non-accessible, since the default value is already false.

This is a partial revert of TextureGroup#1941

The change in TextureGroup#1941 has caused some issues for us and others (see TextureGroup#1997).
If I set `myNode.isAccessibilityElement = true,` then what ends up
happening is that the table cell wrapper view (_ASTableViewCell) also
has `isAccessibilityElement = true`. But then when iOS goes through the
hierarchy it identifies the table cell wrapper view as the target and
attempts to use that accessibilityLabel, which doesn't exist
(because it's actually on the nested node view).
So our node's label is never used.

I'm not sure why setting `isAccessibilityElement` in `_ASTableViewCell`
was necessary in TextureGroup#1941 in order to make a node non-accessible,
since the default value is already false.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant