When comparing Live.js vs CSS refresh, the Slant community recommends Live.js for most people. In the question“What are the best cross-browser live-update / synchronization tools?” Live.js is ranked 6th while CSS refresh is ranked 9th. The most important reason people chose Live.js is:
Once the monitored .css file is saved, changes are implemented without reloading the whole page.
Ranked in these QuestionsQuestion Ranking
Pros
Pro CSS injection
Once the monitored .css file is saved, changes are implemented without reloading the whole page.
Pro Multiple browser support
Live.js has multiple browser support, it supports Chrome, Firefox, Opera, Safari and IE6+. Basically almost all the browsers that are currently in use.
Pro Easy setup
Setting up Live.js is extremely easy, the developer either adds the live.js script inside their page, or if they want to monitor only CSS changes, they can add the bookmark that is found on the Live.js homepage.
Pro CSS injection
Once the monitored .css file is saved, changes are implemented without refreshing the whole page. Only the CSS is changed.
Pro Easy setup
To use CSSrefresh, all that is needed is to include the small .js file or to use the bookmark provided by the CSSrefresh page.
Cons
Con No cross-device support live or otherwise
Does not have support for multiple devices or multiple browsers for live reloading.
Con Only for CSS
CSS refresh only watches for .css file changes. It does not watch for JavaScript or HTML updates.