Skip to content

chore: remove onStartShouldSetResponder workaround from :active examples#9918

Draft
MatiPl01 wants to merge 1 commit into
@matipl01/css-hover-svg-pointerfrom
@matipl01/remove-active-responder-workaround
Draft

chore: remove onStartShouldSetResponder workaround from :active examples#9918
MatiPl01 wants to merge 1 commit into
@matipl01/css-hover-svg-pointerfrom
@matipl01/remove-active-responder-workaround

Conversation

@MatiPl01

@MatiPl01 MatiPl01 commented Jul 9, 2026

Copy link
Copy Markdown
Member

Removes the onStartShouldSetResponder={() => true} workaround from the regular-view :active / :active-deepest examples, now that Android press pseudo-selectors are driven from the window observer (stacked on #9879).

The four SVG examples keep the prop until SVG :active without a responder is checked on device.

Now that press pseudo-selectors are driven from the window observer, the
onStartShouldSetResponder workaround is unnecessary for the regular-view
:active / :active-deepest examples. The four SVG examples keep it pending an
on-device check of SVG :active without the responder.
@MatiPl01 MatiPl01 force-pushed the @matipl01/remove-active-responder-workaround branch from a220fd0 to 7ecb069 Compare July 9, 2026 12:12
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.

1 participant