Closed Munter closed 12 years ago
@walling: Turns out Adblock for Chrome likes to inject a data:
url stylesheet, which wasn't being filtered, and that freaked out fs.watch
on Windows.
If you're using Chrome with AdBlock that would explain your troubles. In that case, could you please try again with livestyle 0.0.12? It works for me in Windows 7 now.
I tested livestyle 0.0.14 in Chrome on Windows 7 with and without AdBlock Plus enabled. The first change in the CSS (after I start livestyle) is applied correctly, but after that it doesn't update the CSS anymore. There is no error traces / messages from the livestyle server and in the Chrome console.
When I refresh the web page, the next change in the CSS is applied as well and then it stops working. I don't need to restart the livestyle server.
@walling: We just added a debug mode (included in 0.0.14), could you try again with livestyle --debug
and gist the output?
@walling: The debug mode also logs a bunch of useful info in the client (goes to console.log
). Would be very helpful if you included that in the gist, too :)
https://gist.github.com/1901214
The funny thing is that the client seems to get the event that the CSS file changed, but it is not updated in the browser.
Maybe it has something to do with the change event firing twice. Why is that? :-)
@walling: Thanks a lot, turned out I could reproduce it with node 0.6.x. I'm usually stuck on 0.4.12.
I tested livestyle 0.0.16 with node 0.6.8 on windows 7 and it works great! Actually I'm going to use it today on some website design I'm doing.
Great. Thanks for your patience so far :)
I hope 2259241 fixes this. Can someone confirm?