You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
Summary was: CSS 3 parser errors aren't skipped over
It will skip over these unparseable sections in normal CSS minification,
however, they will stop CSS combining because we ran into issues where if one
CSS file was actually broken, combining with the rest would break them too.
However, this is overly pessimistic. We should be able to parse the structure
well enough to successfully combine even when there are unparseable sections.
Original comment by sligocki@google.com on 12 Nov 2012 at 11:02
Changed title: css_combine overly pessimistic (should combine even if CSS cannot be fully parsed)
I have a fix checked into svn trunk (that will go into the next release). I
don't know that it specifically solves your combiner case, but it should make
the CSS combiner much more lenient. Now it will only fail to combine CSS files
which are really broken (like mismatched {}s or trailing chars at the end, etc.)
Original comment by sligocki@google.com on 7 Dec 2012 at 11:46
Original issue reported on code.google.com by
amat...@gmail.com
on 12 Nov 2012 at 10:56The text was updated successfully, but these errors were encountered: