ghost
commented
6 years ago Is there any whitespace before your doctype? Could be same as #1299
Open Mil00Z opened 6 years ago
ghost
commented
6 years ago Is there any whitespace before your doctype? Could be same as #1299
iFallUpHill
commented
6 years ago @KeironLowe92 Thanks! That solved my problem.
Mil00Z
commented
6 years ago I worked on Professionnal project : i'm the only one who use this workflow and i don't have the 'hand' on the doctype files because isn't my task.
Also i have the "same" beug on personnal local/server project... i gonna try to fix this with your tips !
Issue details
For several days now, and i don't know why, when I start browser-sync, it isn't auto 'correctly' reload on all viewport i have opened : i have to use CTRL +F5 to apply my change on my all devices to see the changes.
I actually use the UI Interface and the commande 'Reload ALL'
Steps to reproduce/test case
I start my project like this way :
browser-sync start -s -f="css/.css, js/.js,*.html" -b"=Vivaldi" for statics files (testing or anything like that)
OR browser-sync start -p ="my url to watch" -f="css/.css,js/.js,*.html" -b"=Vivaldi"
In Addition:
i use also the path files f="assets/css/.css, assets/js/.js" and more when my project folder are a lil' bit more constructed
i use sass and prepross Software to compil my scss in css folder but i don't understand why this way could be the central point of my beug.
Please provide necessary steps for reproduction of this issue, or better the reduced test case (without any external dependencies).
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
I use brower-sync in a stand alone tools (whitout gulp or equivalence).
If CLI, please paste the entire command below
{cli command here}
for all other use-cases, (gulp, grunt etc), please show us exactly how you're using Browsersync
{Browsersync init code here}