Re: Font-style vs. phrase elements (fwd)
James K. Tauber (jtauber@library.uwa.edu.au)
Wed, 22 May 1996 10:02:29 +0800
Message-Id: <31A275B5.65B7@library.uwa.edu.au>
Date: Wed, 22 May 1996 10:02:29 +0800
From: "James K. Tauber" <jtauber@library.uwa.edu.au>
To: MegaZone <megazone@livingston.com>
Cc: www-html@w3.org
Subject: Re: Font-style vs. phrase elements (fwd)
MegaZone wrote:
> So you want to *force* <DIV> to be used?
Well spotted.
> Why??? Right not the
> implementations I've seen add whitespace, and making headers just the
> first line of a <DIV>? So how about subheaders, I'd need a div on
> each subheader in a FAQ?
You'd need a DIV for each subsection of your FAQ. What's wrong with
that? It makes perfect sense to me. Maybe I misunderstand what you mean
by subheader.
> No thanks, no way in hell I'd use that. There is no reason to force
> DIV to be used dozens of times in a document like that.
If the document has divisions it should have DIVs.
The main flaw I see in my DIV proposal is that it makes nonsense of the
different Hn elements and really requires an H element whose
presentation is determined by the level of the DIV nesting.
But I still don't understand your problem with restrictive DIVs. If you
are marking up a *structured* document, they would be a dream come true.
(If any browser implementors are listening: how would you feel about an
H element that rendered as Hn where n was the level of DIV nesting?)
--
James K. Tauber / jtauber@library.uwa.edu.au
University CWIS Coordination Officer
The University of Western Australia