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

Fix issue where text entry do not have "text field" or a hint in the description #186

Merged

Conversation

DavidBrunow
Copy link
Contributor

Fixes #57. Takes over from #58.

@DavidBrunow DavidBrunow force-pushed the bugfix/swiftUITextFieldMissingDescription branch from 5eb3b40 to c3eb5d0 Compare January 17, 2024 14:17
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@NickEntin FYI this is what I'm getting from VoiceOver on iOS 17.3.

@DavidBrunow DavidBrunow force-pushed the bugfix/swiftUITextFieldMissingDescription branch from e751385 to 391cdd0 Compare January 19, 2024 14:12
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The bounding box for the TextEditor looks off -- on device the element is directly below the last text field and on the leading edge of the screen. If possible I'd like to look into that issue separately from the other issue being resolved in this effort.

@DavidBrunow DavidBrunow force-pushed the bugfix/swiftUITextFieldMissingDescription branch from 391cdd0 to 8485578 Compare January 19, 2024 14:22
@DavidBrunow DavidBrunow marked this pull request as ready for review January 19, 2024 14:23
Copy link
Collaborator

@NickEntin NickEntin left a comment

Choose a reason for hiding this comment

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

This is looking great, thanks for working on this!

@DavidBrunow
Copy link
Contributor Author

@NickEntin do you need anything from me on this? I want to make sure I'm not blocking anything 😄

@NickEntin
Copy link
Collaborator

@DavidBrunow Apologies, been a hectic couple weeks. I'll go ahead and update the snapshot images for you.

@NickEntin
Copy link
Collaborator

NickEntin commented Feb 9, 2024

Ahh looks like the snapshots are flaky cause of the cursor flashing. I think we need to figure out #15 before we land this one. 😕

@NickEntin NickEntin added the blocked This issue or pull request requires another change to be made first label Feb 9, 2024
@NickEntin
Copy link
Collaborator

I think we need to figure out #15 before we land this one.

#206 should resolve this.

@DavidBrunow
Copy link
Contributor Author

@DavidBrunow Apologies, been a hectic couple weeks. I'll go ahead and update the snapshot images for you.

Not a problem and I'm not trying to add pressure, just wanted to make sure there wasn't more I could do 😄

@NickEntin NickEntin removed the blocked This issue or pull request requires another change to be made first label Feb 17, 2024
@NickEntin
Copy link
Collaborator

I think if you rebase this on main the builds should pass now 🤞

@DavidBrunow DavidBrunow force-pushed the bugfix/swiftUITextFieldMissingDescription branch from 1c5a779 to c9a6305 Compare February 18, 2024 03:12
@DavidBrunow
Copy link
Contributor Author

I think if you rebase this on main the builds should pass now 🤞

This is done.

@DavidBrunow
Copy link
Contributor Author

DavidBrunow commented Feb 18, 2024

I think if you rebase this on main the builds should pass now 🤞

This is done.

I did not recapture the snapshots 🤦. I'll do that now, hopefully my machine will capture them right.

Actually I'm going to wait on this since you've mentioned needing to capture them on build machines in the past. Let me know if I need to take any action on this.

@NickEntin
Copy link
Collaborator

NickEntin commented Feb 18, 2024

Ahh yeah, let me pull the images from the CI jobs and update it now. I don't think the iOS 16 job should have failed, so maybe a different problem... 🤔

Copy link
Collaborator

Choose a reason for hiding this comment

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

So I guess this sort of worked in iOS 14, then regressed in later versions. 🤷‍♂️

@DavidBrunow
Copy link
Contributor Author

Ahh yeah, let me pull the images from the CI jobs and update it now. I don't think the iOS 16 job should have failed, so maybe a different problem... 🤔

All checks have passed ✅ 🎉

}
applyVerticalSubviewDistribution(distributionSpecifiers)

textViewWithText.accessibilityFrame = textViewWithText.frame
Copy link
Collaborator

Choose a reason for hiding this comment

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

Was this necessary to fix an issue? This should be the default value.

In any case, accessibilityFrame is defined in the screen coordinate space while the frame is defined in the superview's coordinate space. In a full screen presentation this should generally match, but isn't always the case. We should do the coordinate space conversion here (if we need to keep it):

Suggested change
textViewWithText.accessibilityFrame = textViewWithText.frame
textViewWithText.accessibilityFrame = UIAccessibility.convertToScreenCoordinates(
textViewWithText.frame,
in: self
)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I copied this over from the previous implementation in #58. I don't see why it would be needed. I'll remove it and see if there are negative side effects.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've removed that line.

@NickEntin
Copy link
Collaborator

Thanks David, this looks great! I'll do one final pass to make sure we're good to merge.

One last thing: have you signed the contributor license agreement?

@DavidBrunow
Copy link
Contributor Author

Thanks David, this looks great! I'll do one final pass to make sure we're good to merge.

One last thing: have you signed the contributor license agreement?

I have not, working on that now.

@DavidBrunow
Copy link
Contributor Author

Thanks David, this looks great! I'll do one final pass to make sure we're good to merge.

One last thing: have you signed the contributor license agreement?

FYI I will not get this done tonight, checking with folks at work to ensure there are no issues.

@DavidBrunow
Copy link
Contributor Author

Thanks David, this looks great! I'll do one final pass to make sure we're good to merge.
One last thing: have you signed the contributor license agreement?

FYI I will not get this done tonight, checking with folks at work to ensure there are no issues.

@NickEntin I have signed the contributor license agreement.

Copy link
Collaborator

@NickEntin NickEntin left a comment

Choose a reason for hiding this comment

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

Awesome, thanks for working through this @DavidBrunow! Really glad to see this fixed.

@NickEntin NickEntin merged commit f039d27 into cashapp:master Feb 23, 2024
9 checks passed
@DavidBrunow DavidBrunow deleted the bugfix/swiftUITextFieldMissingDescription branch February 23, 2024 04:38
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.

UITextView and UITextField don't record Voice Over Descriptions
2 participants