You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.
I am seeing the following behavior with regard to tabs, but i would assume this issue might be present elsewhere?
Specific to iPhone models that support force touch, or 3D touch as they call it ... i.e. resulting in events that fire depending on how hard you physically press the screen...
When force pressing a tab the following behavior occurs:
— Initial force press displays a popover like preview of the resulting link.
— Force pressing further will minimize the app and then redirect the user to the mobile Safari browser and loads the resulting link there instead.
Obviously a quick solution would be to disable force touch for the entire application, but what if we want to implement force touch features into our apps?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am seeing the following behavior with regard to tabs, but i would assume this issue might be present elsewhere?
Specific to iPhone models that support force touch, or 3D touch as they call it ... i.e. resulting in events that fire depending on how hard you physically press the screen...
When force pressing a tab the following behavior occurs:
— Initial force press displays a popover like preview of the resulting link.
— Force pressing further will minimize the app and then redirect the user to the mobile Safari browser and loads the resulting link there instead.
Obviously a quick solution would be to disable force touch for the entire application, but what if we want to implement force touch features into our apps?
The text was updated successfully, but these errors were encountered: