I am working on a 3-column fluid layout as well and have the skin compatible in IE, Netscape, Mozilla, Safari and Opera.  I am just beginning to work on the containers.  It has taken a few weeks for me to get this to work but it is completely stable.  You should also be aware that the "expand" and "collapse" buttons of the control panel have a bug - so refer to my posts under "CSS in Multiple Browsers."

I would be happy to send you the style sheets and skin in its current form.  Keep in mind some of this needs to be refactored but the fluid layout works perfectly.  I currently have it configured to max out at 1600px.

http://www.chill-n-go.biz

The site isn't pretty.  But then I don't do the artwork.  LOL

I may have chimed in already but I always feel the need to reinforce my perspective on this...

Noone can really argue that CSS / DIV based layouts are more efficient, cleaner, and where browser technology is headed. However, the problem that I see coming up is the fact that no matter what you do to create a pure CSS based site, you still have to deal with the fact that many of the modules output table-based data. So to me, this seems like an exercise in futility for the moment while the rest of the developer community start to implement more CSS pure modules. Let's not forget DNN's origins as a ASP.NET proof-of-concept and the fact that we have a great community of volunteers and project managers, but major changes like this can take alot of time to roll out and are very dependent on more immediate user needs (SSL, new frameworks, stability issues).

So, in the meantime I still maintain my own Pure CSS skin project, however many of my production sites are still very table-heavy to allow for faster production and happy customers. However if it was a stated requirement for a project I would put forth every effort to meet said requirement.

~SB