-
Notifications
You must be signed in to change notification settings - Fork 755
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
Proxy in Firefox Prevents Navigation #1570
Comments
I'm having the same problem, only occurs when the page I'm trying to navigate is not loaded instantly Edit: A temporary solution is to open the page in a new tab |
I can confirm this, and tried adding 'reloadOnStart: false;' from previous bug fix with no luck. |
Indeed, there seems to be a regression. I also have Yet, 2.24.5 is still messing up navigation in Firefox. I will downgrade to 2.23. |
npm install browser-sync@2.23.7 |
awesome, working like a champ |
I had the same issue usign 2.24.6 and the strange thing is that with the simple Firefox I could navigate the site normally but when I use Firefox Developer Edition I got the same error. Now I've rolled back as suggested by @moaxey but I would like to undestand better why this is happening. |
I had the same problem with both Firefox and Firefox Developer Edition, and can confirm that rolling back to 2.23.7 fixed it. |
Until BrowserSync/browser-sync#1570 is fixed
Is someone looking into this to fix it? Can't be so difficult when it was working until 2.23.7 |
Could the fix for #1591 have any effect on this issue (since it was also related to unexpected reloads)? Have been working with https://github.com/BrowserSync/browser-sync/releases/tag/v2.26.0 for the last hour and haven't seen any unexpected reloads or navigation issues in Firefox or Firefox Developer Edition... |
@abmaonline yeah good spot - this will also be fixed in 2.26.0 :) |
I found this problem has returned in version 2.24.4 of BrowserSync. I rolled the version back to 2.23.6 (because that was a previous project where I knew it was working ok), and the problem went away.
Full details in the original issue:
#386
The text was updated successfully, but these errors were encountered: