Sorry.  Second time in a week I've had to deal with a module that breaks my skin because the tables it outputs clash with my skin code and trashes the designs.  This isn't a tables versus CSS fight, but more "Why can't module developers make them inherit skin settings or at least provide skinning resources?" Yes, I can rework the skin to account for it, but that kind of defeats the purpose of modules and skinning, doesn't it?  Separation of design and content my tookus.  The one I had to deal with last week had hardcoded background settings and I didn't have the source.  The core modules are not home free in these matters either, even they don't behave as a perfect skinning scenario would have them behave.

Sigh...

Jeff

This is indeed a very irritating. What works for me is the following:

Whenever a module developer put something in his module in the form of: < p style="background-color: red" >...< /p >, or < p align="right" >...< /p > 

(the spaces in the html tags are here on purpose, i.e. to make sure you can read this post correctly)

I specify the following in my skin.css:

p
{
    background-color: Blue!important;
    text-align: left!important;
}

Not the use of "!important" This works in many cases. I know it is a work-a-round, but still you don't need to modify the module.

Peter

I didn't think of bypassing these with PageBlaster.  What a wonderful piece of software.  :)

Thanks,

Jeff