I am not going to maintain a list of all possible secondary tests that fail on all possible individual parsing errors, that is way too much work. If your book has parsing errors, then fix those errors first and re-run check book.
Since it makes absolutely no sense to not re-run check book after fixing errors (other wise how do you know the error was actually fixed) I dont see the problem.
And the check should not be aborted after css errors, that was an oversight.
|