213 2003-05-24 06:22:20 +0000 style for errors, warnings... 2005-06-02 07:00:18 +0000 1 1 1 Unclassified Validator Website 0.7.0 Other other RESOLVED FIXED P2 normal 0.7.0 1393 856 1 ot ot www-validator-cvs oldest_to_newest 488 0 ot 2003-05-24 06:22:20 +0000 Work on styling to distinguish - pre-process warnings (no charset/doctype) - parsing errors - parsing info 2197 1 link 2004-09-01 13:00:41 +0000 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). 2366 2 nick 2004-09-20 21:14:15 +0000 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? 2784 3 ot 2005-01-05 02:05:43 +0000 [admin test, pls ignore] 3253 4 ot 2005-05-16 08:37:20 +0000 Started work on this. Styling the parsing warnings depends on them being given at all as output, so putting dependency on currnet Bug #1393 3263 5 ot 2005-05-17 01:16:51 +0000 (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. 2999 6 ot 2005-06-02 07:00:18 +0000 (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