Skip to content

Commit

Permalink
Document change in behaviour wrt not ordering css files
Browse files Browse the repository at this point in the history
  • Loading branch information
canton7 committed Jul 2, 2011
1 parent e92145b commit 71234d8
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions readme.md
Expand Up @@ -319,8 +319,8 @@ echo Casset::render_js(false, false, array(), true);
When minifying CSS files, urls are rewritten to take account of the fact that your css file has effectively moved into `public/assets/cache`.
With JS files, changing the order in which files were added to the group will re-generate the cache file, with the files in their new positions. However with CSS, it will not.
This is because the order of JS files can be important, as dependancies may need to be satisfied. In CSS, no such dependancies exist.
With both CSS and JS files, changing the order in which files were added to the group will re-generate the cache file, with the files in their new positions.
This is because the order of files can be important, as dependancies may need to be satisfied.
Bear this in mind when adding files to groups dynamically -- if you're changing the order of files in an otherwise identical group, you're not allowing
the browser to properly use its cache.
Expand Down

0 comments on commit 71234d8

Please sign in to comment.