W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 1999

Re: h1, h2, etc. (+ pwWebspeak)

From: Charles F. Munat <coder@acnet.net>
Date: Fri, 15 Jan 1999 17:26:57 -0600
Message-ID: <00ce01be40de$918236e0$291172a7@acnet.net>
To: "Pawan Vora" <pvora@uswest.com>
Cc: <w3c-wai-ig@w3.org>
Pawan Vora wrote:
"You can get the indents... but it's not considered "good"
html code.
Here are two different ways:

1. starting a paragraph with <DD>
2. starting the paragraph with a bunch of &nbsp;'s ... so
you can do
&nbsp;&nbsp;&nbsp;&nbsp;This is my second paragraph.

Of course, the third option is to try the "single-pixel" gif
trick....
but, that's not good design either!"

------------------

You can also use CSS to achieve the indent. I'm not that
worried about backwards compatibility because I can adjust
the pages dynamically based on the browser. It's the blank
lines that bother me. I can't seem to override them.

In the past I've used DIV tags to avoid the blank lines and
non-breaking spaces or CSS to indent the first line. The
single pixel gif takes a performance hit (small though it
may be), so I've preferred the non-breaking spaces. Some
browsers, however, like pwWebspeak, compress even the
non-breaking spaces, so you don't get much of an indent. I
am also curious as to why pwWebspeak, seemingly alone among
browsers, does NOT insert blank lines between P elements.
Maybe if Mark reads this he can explain.

Actually, I've had the most problem getting decent looking
text on pwWebspeak. Since the browser is clearly intended to
be used by those with low vision (thus the yellow on black
big text), why does it lay pages out in such a dense,
difficult to read (for me, anyway) manner? Another of life's
great mysteries.

Charles Munat
Received on Friday, 15 January 1999 18:36:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:43 GMT