This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Work on styling to distinguish - pre-process warnings (no charset/doctype) - parsing errors - parsing info
We should probably look into defining a set of categories for messages to fall into, and design suitable CSS accordingly. This would be a very good thing to get done for 0.7.0 (setting blocker accordingly).
Yes indeed distinguish preprocessing from processing messages. But distinguishing different messages from OpenSP (beyond W/E/I/etc) is going to require a lot of thinking. Is that really what you have in mind, or do you just mean applying 'class="E"' to a warning?
[admin test, pls ignore]
Started work on this. Styling the parsing warnings depends on them being given at all as output, so putting dependency on currnet Bug #1393
(In reply to comment #1) > We should probably look into defining a set of categories for messages to fall into Not sure how that would be feasible beyond the realm of Error/Warning/Info (which, conveniently, is what SP is using - as niq notes in comment #2). Now that bug #1393 is being fixed, I have made a basic implementation stating what kind each parsing message is, and giving different styles/colors for each (red for errors, subdued, pinkish red for warnings, and neutral grey for info). Will give myself a day or two for a potential cleanup and tweaks, and will then close if no-one opposes the fix as implemented.
(In reply to comment #5) > Will give myself a day or two for a potential cleanup and tweaks, and will then close if no-one opposes > the fix as implemented. Hearing no objection, closing