MobileRead Forums - View Single Post

JSWolf · 06-10-2013, 05:21 PM

The problem is that FlightCrew needs updating so there would not be a need to use the W3C CSS validator. The problem with the validator level that's being used is that it's telling the user that perfectly valid @font CSS code is an error and if the person is not experienced enough, this could cause no end of trouble trying to get the CSS to validate without error. So the way to do this is to either change the CSS validation level or fix FlightCrew.

However, what could also be done is if anything is in the CSS like @font that won't validate with 2.x, use 3.x and if nothing is in the CSS that won't be an issue to 2.x, use 2.x.

But don't do anything that tells the user that valid code is in error.

06-10-2013, 05:21 PM	#29
JSWolf Resident Curmudgeon Posts: 80,212 Karma: 148951761 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	The problem is that FlightCrew needs updating so there would not be a need to use the W3C CSS validator. The problem with the validator level that's being used is that it's telling the user that perfectly valid @font CSS code is an error and if the person is not experienced enough, this could cause no end of trouble trying to get the CSS to validate without error. So the way to do this is to either change the CSS validation level or fix FlightCrew. However, what could also be done is if anything is in the CSS like @font that won't validate with 2.x, use 3.x and if nothing is in the CSS that won't be an issue to 2.x, use 2.x. But don't do anything that tells the user that valid code is in error.