Hello Yvonne
Because when BusinessCSS was first developed 5 years ago, we didn't really fully understand the full implications of CSS. So we didn't implement as purely and efficiently as some people would like. You can safely remove (or comment out) all content from the <body> tag other than
The reason we haven't removed this code is that it doesn't do any serious harm to the design (and is easily removed) but if we decided to 'clean-up' our default themes, it makes people's designs much harder to upgrade to the latest version. We decided that the slight disadvantage of having this code still in the <body> tag, is far outweighed by the benefits of not having your primary template upgraded by the Actinic Upgrader.
Believe me, I have no love affair with nested tables, and I agree that we have rather overdone tables in the past. But on the plus side, tables in general are robust, reliable, work across a wide range of web browsers consistently and understood by a wide range of the web design community. They also work brilliantly with a templated system like Actinic as they can grow and stretch in expected ways when data is placed within them.
But they are perceived as being out of date by the web design community, and they are also incompatible with the W3C guidelines which state that tables should only be used for tabular data. They are also not great for people using screen reading devices.
So, over the last year or so I have been involved with learning CSS-based standards-compliant design and figuring out how to use it best with Actinic. So in a future version of Actinic you should see designs that are more to your liking.
Why in the world is the body tag for BusinesCSS filled with formatting???
Code:
onLoad="NETQUOTEVAR:ONLOAD"
Second, why this love affair with nestled tables? Even when they don't make the least sense they're there. It's a pain to strip off all the excess tables and sometimes it's not even possible without creating untold horrors. Like Ted I keep ripping and ripping and ripping...
But they are perceived as being out of date by the web design community, and they are also incompatible with the W3C guidelines which state that tables should only be used for tabular data. They are also not great for people using screen reading devices.
So, over the last year or so I have been involved with learning CSS-based standards-compliant design and figuring out how to use it best with Actinic. So in a future version of Actinic you should see designs that are more to your liking.
Comment