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

Ax parent #190

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Ax parent #190

wants to merge 5 commits into from

Conversation

jzucker2
Copy link
Contributor

This is a proposed solution to this issue: #189

Need to fill out subliminal methods for abstracting these
concepts.
This has basic docs (needs fleshing out). But a working version
of a solution for child and parent accessibility elements, along
with implementations for UINavigationBar and UITableViewCell.
@jzucker2 jzucker2 mentioned this pull request Apr 24, 2014
On iOS 6, table view cells themselves appear in the accessibility
hierarchy. On iOS 7, mock cells (instances of
`UITableViewCellAccessibilityElement`) appear in the hierarchy
instead.
Documented view and accessibility view heirarchy for iOS 6 and 7
for UITableViewCells. It is slightly different and needed to be
accounted for.
Extended to all elements and allowed `SLTableViewCell` to
override.
@@ -376,6 +376,9 @@ @implementation UITableViewCell (SLAccessibilityHierarchy)
- (BOOL)classForcesPresenceOfMockingViewsInAccessibilityHierarchy {
return YES;
}
- (BOOL)classForcesPresenceInAccessibilityHierarchy {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious to see that you reverted the version-specific checks. Is there no difference between versions? How can both instances and their mock views be present in the hierarchy? (It'd be nice to describe whatever the answer is in a comment in the source.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also can you add case(s) to SLElementMatchingTest exercising whatever this addition fixed?

@wearhere
Copy link
Contributor

wearhere commented May 5, 2014

You've made the core functionality here pretty elegant @jzucker2! 👍 Most of my feedback is about making the tests as straightforward:

  • removing the debug code i.e. the logs and screenshots
  • testing the new classes in addition to their use as child element constructors
  • testing that we've matched particular children rather than similar elements elsewhere in the hierarchy

Thanks for iterating on this.

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.

2 participants