I should really jump on the clearfix train. It's 2010. I'm sure some browsers MUST support it by NOW.
Yeah, that was sarcasm =P Glad you got what you needed, Oranuf. =) -LT On Tue, May 4, 2010 at 5:02 PM, oranuf <[email protected]> wrote: > Thanks - the clearfix seems more like what I should do. > > So the general rule then is that if I want to have two divs as > "columns" in the context of a larger layout of any kind, they need to > be in a container with a class of "clearfix" applied? Always? > > Also -- the inline CSS goes away once I have the layout/design for the > widget the way I want it. I start out inline so I don't need to > bounce back and forth between files in my editor -- especially when > I'm fighting with something. :) > > Thanks to ALL of you -- amazingly fast answers, all of which were very > helpful. > > > Or you could add class="clearfix" to a div with id of > > #PollQuestionaireContainer so it's more in blueprint spirit and > > content will not be hidden if it doesn't fit in. > > > > When the content is floated the container doesn't always want to > > stretch enough to accommodate the content so you need to force it to > > do so. Try to read up on "clearing floats". > > > > And finally a suggestion, don't use inline css if you don't have to. > > > > -- > You received this message because you are subscribed to the Google Groups > "Blueprint CSS" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<blueprintcss%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/blueprintcss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en.
