-
Notifications
You must be signed in to change notification settings - Fork 42
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
Refresh not triggered automatically on mobile devices #29
Comments
@tinesoft sorry for the delayed reply. as reloading works fine on PC and fails on mobile, i guess this is the browser-sync issue. but, if "Rebuilding..." is displayed, it becomes even more strange. did you try testing this on different phones (running iOS, for instance)? cheers |
Hi @Va1, Unfortunately i don't have any other mobile phones to test on, just my Android phone with Chrome... |
Can confirm. Also |
@nmihaica I managed to get hot reloading to work on mobile, now just having trouble with onChange events on inputs not syncing. |
I dropped |
I changed reload: false to reload: true and it appears to work as intended. |
hi! i also have the same issue. does anyone have a solution besides changing the "reload" option? |
Same issue for me, I need HMR for my css but I don't want to reload the browser because the page is relatively heavy (lots of pictures). |
Hi,
I'm using this
browser-sync-webpack-plugin
(along with gulp+webpack-dev-server) to run an Angular application built with Angular CLI.The plugin config is the same as default:
Almost everything works pretty well.
BrowserSync
proxies towebpack-dev-server
, its features like scroll synchronization, CSS outlines, CSS grids, work great across browsers/devices (tested with Chrome, Chrome Android and Firefox).The plugin DOES detect changes from
webpack-dev-server
, and refresh the page on PC browsers.But the refresh is not triggered automatically on my mobile browser (Chrome Android v.57.0.2950.3).
even if the "Rebuilding..." message is correctly displayed.
Any ideas?
Thanks in advance
The text was updated successfully, but these errors were encountered: