-
Notifications
You must be signed in to change notification settings - Fork 24.7k
Fix Facsimile Hit Testing Bugs #52065
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D76764051 |
This pull request was exported from Phabricator. Differential Revision: D76764051 |
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
8bc3a0f
to
4e417cd
Compare
This pull request was exported from Phabricator. Differential Revision: D76764051 |
4e417cd
to
574322e
Compare
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
This pull request was exported from Phabricator. Differential Revision: D76764051 |
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
574322e
to
fc30c94
Compare
This pull request was exported from Phabricator. Differential Revision: D76764051 |
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
fc30c94
to
20d8805
Compare
This pull request was exported from Phabricator. Differential Revision: D76764051 |
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
20d8805
to
8c6355a
Compare
This pull request was exported from Phabricator. Differential Revision: D76764051 |
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
8c6355a
to
f69c04d
Compare
This pull request was exported from Phabricator. Differential Revision: D76764051 |
f69c04d
to
9d072ac
Compare
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
This pull request was exported from Phabricator. Differential Revision: D76764051 |
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
9d072ac
to
36ae029
Compare
Summary: Pull Request resolved: facebook#52065 1. We can crash when tapping at the boundary between two spans. Previous ReactTextView had some custom heuristic for overlapping ReactTags, assuming they could be nested, which never happens (We only have a single tag per AttributedString fragment), but spans may overlap at a single character, where one is meant to be exclusive, and the other inclusive. We add logic for that. 2. We don't incorporate the offset of the text layout within the view for hit testing, needed for padding or `textAlignVertical`. Changelog: [Internal] Reviewed By: joevilches Differential Revision: D76764051
This pull request was exported from Phabricator. Differential Revision: D76764051 |
36ae029
to
f798971
Compare
This pull request has been merged in 64ce769. |
This pull request was successfully merged by @NickGerleman in 64ce769 When will my fix make it into a release? | How to file a pick request? |
Summary:
textAlignVertical
.Changelog: [Internal]
Reviewed By: joevilches
Differential Revision: D76764051