css syntax error masks missing resources

[GoogleCodeExporter]

If my css file has any syntax error in it, such as a missing brace or bad 
selector, no errors are reported by epubcheck for the publication.

If I fix the syntax error, missing resources referenced in the css file are 
then reported as errors.

I assume the invalid css file causes further checks to be skipped, but odd that 
no error about the file itself being invalid is generated.

I discovered this in an old version of Accessible EPUB 3 that was missing 
referenced fonts. The latest version in the repository has been fixed, but you 
should be able to put any reference to a non-existent font into a file to 
recreate.

Original issue reported on code.google.com by mgarrish on 15 Nov 2012 at 3:42

[GoogleCodeExporter]

Original comment by markus.g...@gmail.com on 25 Nov 2012 at 9:24

• Changed state: Accepted
• Added labels: Milestone-3.0.0, Priority-Medium, Type-Defect

[GoogleCodeExporter]

This issue was closed by revision r375.

Original comment by markus.g...@gmail.com on 25 Nov 2012 at 9:38

• Changed state: Fixed