The height is constraining the box...
I think you have two choices:
add overflow : hidden|auto (will hide or scroll excess content)
remove the height attribute and control height some other way.
Good Luck.
On Fri, 15 Oct 2004 15:35:14 +1000, Natalie Buxton [EMAIL PROTECTED] wrote:
Hi
There is a height set on the .floatleft class of 240px on the page you
listed in your msg.
Tania
- Original Message -
From: Natalie Buxton [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, October 15, 2004 2:21 PM
Subject: Re: [WSG] Text Escaping from Floats
On Fri, 15 Oct 2004
scrap that - it now works as expected.
Thanks for pointing out the height!
It doesn't work in my real-world code (not uploaded) though - must be
some other element in the actual page causing the issue.
Thanks again.
On Fri, 15 Oct 2004 17:07:36 +1000, Natalie Buxton [EMAIL PROTECTED] wrote:
hi Natalie,
just delete the height rule from the .floatleft div. that way the
divs will expand to contain the text.
in fact, Mozilla and Firefox are behaving exactly as the standards say
they should - it's IE that is getting it wrong by expanding the div
beyond your stated height.
On Fri, 15
Hi all,
Apologies if this has been asked on WSG before, but I was wondering
the general opinion on the most correct semantic way of coding
breadcrumb trails.
There's many webpages dealing with this:
http://www.simplebits.com/notebook/2004/02/23/sqxii_conclusion.html
In most legal documents the number is very important and is referenced
in dozens of places, other documents etc.
For this reason I'm not sure if ols even with css 3 support are that
suitable beyond the inital creation of the document.
I'd just use a h11 main section/h1
and h21.1 not so main
On Fri, 15 Oct 2004 18:43:08 +1000, Gavin Cooney wrote:
So what do you think? How do you do your breadcrumbs?
Option 1 - ul list.
Simple to do and applies some semantics to it, without using too much
bandwidth or work.
Option 2 (nested ul) and 3 (ol) actually have stronger arguments for
them,
Option 4 is... interesting. There is something subtlely wrong with it,
but I can't quite put my finger on it. Perhaps it just seems overkill?
I think at this stage i'm an option 4 convertee... unless you can
convince me otherwise!
It just seems the most semantically correct... turn off styles
Option 3 for me, on the grounds that yes, it's a list, but that the
order of the list items is important (as it effectively denotes a
step-by-step path from the site's home page to the current page, and
these steps need to be taken in that particular order). It's this
hierarchy inherent in the
in my opinion this is still rather sketchy, i am yet to see some
examples where people are using this technique in the realworld. yes
there are a lot of 'how to' on the w3c site but i am more interested
in the realistic examples. But anyway thanks for your replies guys. It
would be good to see if
I think I understand...
You want to make the semi-transparent div cover the entire window, and
to remain covering the window on window.onresize.
Moz will do this for you using CSS only, provided it is not contained in
another element with positioning, or the containing element is body:
/* css
I was having a great week in my Mac world of coding my newest client's
website in CSS XHTML. All was well in my happy little MacLife. The
site was working just fine in Mac Safari, Firefox, Netscape, IE
5.2.3. Then I got curious as to what was going on in the PC world. So
I went to a
12 matches
Mail list logo
