On Sep 30, 2007, at 3:25 PM, William M Conlon wrote:
> The text in the two lower columns is not likely to change much, so I
> can live with the padding approach, but I'm curious if there is a
> better alternative.
One way you might achieve this is to give #bottom relative
positioning and absolu
William M Conlon wrote:
> I'm working on a new layout at http://new.ggfilms.com/
>
> using http://new.ggfilms.com/css/styles.css
>
> I have two sets of columns. The upper set aligns vertically at the
> top with each other as desired.
>
> The lower set of columns is supposed to align at the botto
It's so you can write different styles for the different sections of
the site.
.section_products #sub div.section { ... }
.section_about #sub div.section { ... }
It's also useful when it comes to highlighting links in navigational
menus.
.section_products #nav_main li
I'm working on a new layout at http://new.ggfilms.com/
using http://new.ggfilms.com/css/styles.css
I have two sets of columns. The upper set aligns vertically at the
top with each other as desired.
The lower set of columns is supposed to align at the bottom, with
each other, and this is pro
Don Stefani wrote:
> .bodyClass #header #nav #navlist { ...
>
> Is this done to insure that older browsers will follow the path to
> the markup and css?
No. Selector-chains like that will add specificity and target-precision
in multi-container layouts, but that's the same in old and new browsers
On 30-Sep-07, at 9:20 PM, Don Stefani wrote:
> While testing out a web building IDE I noticed this about the
> generated CSS:Putting
> a class in the body tag and then using that to preface every
> declaration in
> the style sheet.
>
> IE:
>
> .bodyClass #header #nav #navlist { ...
>
> Is this
While testing out a web building IDE I noticed this about the
generated CSS:Putting
a class in the body tag and then using that to preface every declaration in
the style sheet.
IE:
.bodyClass #header #nav #navlist { ...
Is this done to insure that older browsers will follow the path to the
mark