Cameron
Its not that I dont care about validation, I just try and make as much valid as possible without having to modify core code, except for the realy special proects.
I make sure that my skins is valid xhtml to be sure that if i use a tableless skins with floated divs that they are correctly rendered on almost any browser and with teh css portals that I did this is the case and thats the most important to me.
as an added bonus, that was mean in a cynical way. meaning that even if you can get it to work nicely you will always have validating errors because of asp.net 1.1
I make sure all my xhtml validates in certain portls by using the telerik controls and the telerik editor . I have been using and implmenting these since ibs days ( made me telerik MVP ;)
This is why I bother with the best attempt, out of the box dnn doenst work with tableless skins and with a few modifications it does. I started out with basic css ksins and added some dnn only hacks and now i have a nr of large portals runnign on them.
At least I know the validation errors that are generated are notmy fault. And i can live with that, after all it may seem like a lot of errors but they are all duu to the rendering of uppercase tags,invalid html declaratiosn in the generated pane code and nome other trivial issues
Armand Datema
Get my new skin ( lots of design variations [18 headers, 30 titlebars, 30 breadcrumbs, 3 footers ], 50+ typography containers , 50+ page templates and an online theme builder for unlimited skin variations) Aura>
For all your skin conversions
2DNN
Follow me on Twitter