Uhh, yeah, well you see... thats the thing... *runs and hides*

CSS for "table" layouts is overrated....

Tabular data should always been enclosed within a table. Non-tabular data should not. I don't need tables to house the tables that house the tables, et al.

Well, considering there's no 'pirated' release of vBSEO3 -- you'd have to have used a vBSEO2 release, which many people have 'massaged' to work on their vB3.x forums. In which case, it's not a fair comparison. :p

It's all just tags; div tag, table tag - who cares. You say tables shouldn't be used, I say it makes no difference if the end result is the same; although tables are more widely supported by browsers still in use.

It's a preference, not a requirement.

They could implement some more ajax functions :)

SEO is a bad idea in my oppinion.

Pm themselves agreed although should be an option..

Report own posts.. No because they might say oops wrong section or simular things..

Who said tables shouldn't be used? Not me.

Tables should be used where there is tabular data. Not to format a page. There's a happy medium between CSS and tables. Currently, vBulletin tables is the equivalent of me using 100% CSS. Pointless and ineffecient.

And yes, right now, it is a preference. However, as web trends continue CSS will be the new requirement. Why wait until then? Do you still use depreciated tags in your HTML?

I really hope this thread doesn't turn into one arguing about CSS & Tables.

Rework of the calendar would be great ;)

PostgreSQL DBMS driver or at least the ground work in place so I can make one myself without changing just about every file.