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

Safari 11 : Router does not work as expected #16095

Closed
gramsco opened this issue Aug 11, 2020 · 3 comments
Closed

Safari 11 : Router does not work as expected #16095

gramsco opened this issue Aug 11, 2020 · 3 comments
Labels
please add a complete reproduction The issue lacks information for further investigation

Comments

@gramsco
Copy link

gramsco commented Aug 11, 2020

Bug report

Could be related to #9851

On our website, we have a closing button of a modal whose clicking should trigger router.back(). This works perfectly in chrome and firefox. Unfortunately, a colleague could not make it work with either safari 11.1 or iOS.

For the time being, I hide the button when the browser is safari.

Thanks!

System information

  • mac OS / iOS
  • safari 11.1
  • Version of Next.js: 9.5.1
@timneutkens timneutkens added the please add a complete reproduction The issue lacks information for further investigation label Aug 12, 2020
@timneutkens
Copy link
Member

Please always follow the complete issue template otherwise issues become impossible to investigate. Please provide a clear and concise reproduction in a github repository.

@gramsco
Copy link
Author

gramsco commented Aug 13, 2020

Sorry for not providing a reproduction repository! I will make sure to do it next time.

The bug was actually provoked by a silent fail from a contemporary window.navigator.vibrate, undefined in both versions (desktop / iOS) of safari. So "issue" closed.

@gramsco gramsco closed this as completed Aug 13, 2020
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
Development

No branches or pull requests

3 participants