IMPROVEMENT: XHTML VALID and CSS VALID buttons

[machadoug]

It would be awesome if all extensions were XHTML and CSS Valid!

To encourage developers to write XHMTL and CSS valid extensions I'm suggesting to put other two MTree custom Field in the Extensions Directory.

It would be great.

Best Regards,

[core2]

I totally support your idea! Have a look at my post one month ago in this forum:

joomla/forum

Cheers!

[machadoug]

No one seems to care!

It's a simple change that would make a great difference.

Best regards from Brazil,

[ot2sen]

Hi machadoug,

Thanks for your suggestion.
Every input and new suggestion made in this particular forum are collected, evalutated and discusssed for future improvement of JED.

Cant say if this idea of yours will fit in the overall presentation. Just wanted to say that we have taken note of it 

[joarvat]

This initiative is allso strongly supported by me.  The only way of finding out whether an extension produces valid XHTML is to install it and try it - which is a bit of a waste.

[mpettitt]

The problem with this is that a lot of extensions rely on what has been entered by the site content editors - the extension might be XHTML Strict 1.0, but if the content has been pasted from an old HTML editor and is full of s and s, the output is going to be invalid when checked.
Likewise for CSS: most extensions come with a basic style, which could well be valid, but as soon as someone who isn't conversant with making valid CSS changes it to fit their site, it could well become invalid.
This might appear to be obvious, but all it would take would be someone who isn't particularly proficient to install something which outputs perfect code into a site that is a mess, then run a validator and complain about the results in extension comments, and the extension developer ends up with poor feedback that doesn't have anything to do with them.