ph-css: Parsers skips more content than browsers in case of error in browser-compliant mode
Hi Philip. So, another issue from the fields. Here’s the excerpt from one CSS file, and the error-handling is slightly different as outlined in comments:
/* correct part */
table.fast th, table.fast td {
padding: 10px 10px;
text-align: left;
}
/* error that should be skipped*/
table.fast th background:#eee;
/* first correct part that skipped by both browsers and parser algorithm */
.ir {
display: block;
}
/* correct part that is skipped by parser but is read by browsers */
div.flexible-detail-left {
margin-bottom: 30px;
}
/* end of skipped part */
.some { more: css; }
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (11 by maintainers)
Commits related to this issue
- Added test for issue #24 — committed to phax/ph-css by phax 8 years ago
- Added tests for issues #22 and #24 — committed to phax/ph-css by phax 8 years ago
- Further fix for issue #24 — committed to phax/ph-css by phax 8 years ago
- Issue #24 fix backport — committed to phax/ph-css by phax 8 years ago
I will do later today 😃