Div hights and fluffy pink elephants

Hello,

http://www.amykimber.com/amy/top.htm
http://www.amykimber.com/amy/styles/style.css

Right... I have two divs at the top that are groovy and fine. The
first one is 20px high, the second 145px. Both are specific highs due to the
images in them, one 20 pixels high, the other 145....

under these two parts I want to move into %s, I want three blocks
(right, left and main). All 80% high - all the same size no matter what the
content, how do I do this?

Please please help, at the moment I've put in a background section
(the black background one), then put my three sections into this to kind of
contain them, hopefully to make them the same size, but they don't seem to
pay any attention to it, just stretch over it....

So, how do get these sections to be the same height?

Many thanks for any comments at all!

Amy K


p.s. yeah, I lied about the elephants

The mockup page lacks a header, for the index page the page header would
be <h1>Amy Kimber, Big Hair, Big Ideas</h1>.

<showignorance>
So there should definitely be an <h1> on an index page? Are there any links
to resources that advise on that? I'm starting to realise that while I can
certainly write HTML that validates, it is far from well-formed.
</showignorance>


P.

"The Plankmeister" <plankmeister_NOSPAM_ (AT) hotmail (DOT) com> writes:

The mockup page lacks a header, for the index page the page header would
be <h1>Amy Kimber, Big Hair, Big Ideas</h1>.

showignorance
So there should definitely be an <h1> on an index page? Are there any links
to resources that advise on that? I'm starting to realise that while I can
certainly write HTML that validates, it is far from well-formed.
/showignorance

Best practice is that there should be a <h1> on every page, containing
the title of the page. Which is not necessarily the same as the
contents of the <title> element of the page, but a lot of the time the
same text in both is appropriate.

Move to the Strict Doctype if you haven't already, that'll make
writing good quality HTML slightly easier because the validator will
pick up on various deprecated elements for you. After that, just make
sure you use elements for the purpose intended (usually the one
implied by the name) - references like the HTML spec at
http://www.w3.org/TR/HTML401/ and the pages at
http://www.htmlhelp.com/ are good for this.

Then once you've got a well-structured [1] HTML file, link in your
stylesheet and make it look pretty.

[1] I prefer this to 'well-formed' since that has a separate and very
different meaning when talking about XML.

--
Chris

On Mon, Sep 15, Chris Morris inscribed on the eternal scroll:

Best practice is that there should be a <h1> on every page, containing
the title of the page. Which is not necessarily the same as the
contents of the <title> element of the page, but a lot of the time the
same text in both is appropriate.

Sort-of, but the title should make some kind of sense even when it's
out of context (e.g as the title of an arbitrary bookmark), whereas
the H1 only needs to make sense within the context of its own page and
web.

Just to take an example: I use three videoconference services. They
all have a page showing relevant bookings. The pages' respective H1
*could* be "Current bookings" or similar. But if that was also their
title, then all three bookmark titles would be the same, which would
be pretty unfriendly.

In fact, I need to know that one of them has the title "DCS reports";
it doesn't have an H1 - its main "headline" is mocked-up using "font
size".

One has the title "Videoconference Booking Service - list bookings",
whereas it identifies the name of the service in its H1, so that's
actually the wrong way around.

And the third is a goddamned frameset where every page on the site has
the same goddamned title. The frame in question doesn't have an H1,
it only has an image of some relatively large text :-( saying "List of
ongoing meetings".

So none of them really meet the criteria :-((

Headless wrote:

Don't use IE to check what you're doing if you are
going to experiment with CSS, it will confuse you to no end. Be aware of
the things that IE doesn't support, then design using a good UA, then
check your work in IE as the last step.

FWIW, I used to take this approach. After being satisfied with results
in various versions of mozilla, Opera, and even NS4 I'd finally get
around to testing IE (usually IE6, in standards mode). It often nearly
brought me to tears the way it botches things. Sometimes I'd have to do
some major rethinking just because of this pathetic excuse for a
CSS-capable browser. :-(

I decided it was better to test it up front, alongside a decent browser,
if I wanted to save myself pain and suffering later on.

--
To email a reply, remove (dash)ns(dash). Mail sent to the ns
address is automatically deleted and will not be read.

The Plankmeister schrieb:

(usually IE6, in standards mode).

Standards mode? How do you do that, then? (My knowledge is increasing
exponentially today!)

Doctype switching...

IE6:
<http://msdn.microsoft.com/workshop/author/css/overview/cssenhancements.asp>
Mozilla: <http://mozilla.org/docs/web-developer/quirks/doctypes.html>
Opera 7: <http://www.opera.com/docs/specs/doctype/>

Some more reading:
<http://gutfeldt.ch/matthias/articles/doctypeswitch.html>


Matthias

"The Plankmeister" <plankmeister_NOSPAM_ (AT) hotmail (DOT) com> wrote

The mockup page lacks a header, for the index page the page header would
be <h1>Amy Kimber, Big Hair, Big Ideas</h1>.

showignorance
So there should definitely be an <h1> on an index page? Are there any
links
to resources that advise on that? I'm starting to realise that while I can
certainly write HTML that validates, it is far from well-formed.
/showignorance

You might find the responses to my post of Mar 21, 2003 interesting. Here's
the link:

http://groups.google.com/groups?hl=e...readm=IuLea.75
94%24by5.1567166570%40newssvr10.news.prodigy.com&r num=1&prev=/groups%3Fq%3Dh
eadings%2Bmcdonald%2Bgroup:comp.infosystems.www.authoring.stylesheets%26hl%3
Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group%3Dcomp.infosystems.www.authori
ng.stylesheets%26selm%3DIuLea.7594%2524by5.1567166 570%2540newssvr10.news.pro
digy.com%26rnum%3D1

Or try searching on the subject "heading depths - use/misuse"

Brian

Els <els.aNOSPAM (AT) PLEASEtiscali (DOT) nl.invalid> exclaimed in <bk4r2f$p7v$8 (AT) reader1 (DOT) tiscali.nl>:

Alan J. Flavell wrote:

And the third is a xxxxxxxx frameset where every page on the site has
the same xxxxxxxx title. The frame in question doesn't have an H1,
it only has an image of some relatively large text :-( saying "List of
ongoing meetings".

Would you mind leaving out the swearing next time?

Sarcasm, and the non-consentual editing of other people's messages, does
not travel well.

--
- Tina Holmboe Greytower Technologies
tina (AT) greytower (DOT) net http://www.greytower.net/
[+46] 0708 557 905

Chris Morris <c.i.morris (AT) durham (DOT) ac.uk> exclaimed in <87wucaf3o1.fsf (AT) dinopsis (DOT) dur.ac.uk>:

showignorance
So there should definitely be an <h1> on an index page? Are there any links
to resources that advise on that? I'm starting to realise that while I can
certainly write HTML that validates, it is far from well-formed.
/showignorance

Best practice is that there should be a <h1> on every page, containing
the title of the page. Which is not necessarily the same as the

Unless, of course, there is no heading in the document that is
more important than all the other headings.

Title, on the other hand, is not the same. The TITLE-element should, per
specs, contain something that describes the content of the document. That
is not necessarily the same as what the most important heading of said
document is.


--
- Tina Holmboe Greytower Technologies
tina (AT) greytower (DOT) net http://www.greytower.net/
[+46] 0708 557 905

In article <lDq9b.28734$dP1.80977 (AT) newsc (DOT) telia.net>,
tina (AT) greytower (DOT) net (Tina Holmboe) wrote:

showignorance
So there should definitely be an <h1> on an index page? Are there any links
to resources that advise on that? I'm starting to realise that while I can
certainly write HTML that validates, it is far from well-formed.
/showignorance

Best practice is that there should be a <h1> on every page, containing
the title of the page. Which is not necessarily the same as the

Unless, of course, there is no heading in the document that is
more important than all the other headings.

Title, on the other hand, is not the same. The TITLE-element should, per
specs, contain something that describes the content of the document. That
is not necessarily the same as what the most important heading of said
document is.

Discussion and opinions:
http://www.simplebits.com/archives/2...rt_v_site_and_
page_titles.html#comments

Conclusions:
http://www.simplebits.com/archives/2...te_and_page_ti
tles_conclusion.html#comments

The kind of quiz there appears every once and a while. The site is a
permanent bookmark for me.

--
Kris
kristiaan (AT) xs4all (DOT) netherlands (nl)
"We called him Tortoise because he taught us" said the Mock Turtle.