Replies: 1 comment 4 replies
-
|
Hey @focux, thanks for the input. Honest answer is: I'm not sure. We have plans for "preventDefault" mechanism, but we're still in talks on how to design it & implement it. With that in place the effect you desire would be achievable, right? If so, then we need couple more weeks to open a PR where we'll be able to discuss the proposed solution in public. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
There’s a pattern emerging with the new iOS tab design where a tab is given a "search" role to make it visually prominent and keep it visible even when the tab bar collapses. Instead of navigating to a standard tab screen, tapping this tab intercepts the action and presents a different screen (usually full-screen and without tabs).
You can see this pattern in several apps, including the GitHub app.
My question is: would you be open to accepting a PR that introduces an API allowing a tab press to not trigger navigation while still emitting the onChange event?
This would make it possible to support this pattern natively instead of relying on patches or workarounds. Would that be something you’d consider accepting?
Here is the patch that I made to support this on my app.
References
https://x.com/Foocux/status/1993466414649450889?s=20
https://x.com/Dimillian/status/1932359777084174575?s=20
Beta Was this translation helpful? Give feedback.
All reactions