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

Re: Fw: Disturbing trend in tables

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 12 Jan 2001 17:32:57 -0500 (EST)
To: Tina Marie Holmboe <tina@elfi.elfi.org>
cc: <jim@jimthatcher.com>, David Woolley <david@djwhome.demon.co.uk>, <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0101121729440.28400-100000@tux.w3.org>
Actually, according to the HTML 4.0 specification it is incorrect HTML. (So
is using tables to achieve layout effects, by the way.) Written into the
Specification and published by the W3C, on the advice of the W3C
members, several years ago now.

The trick of placing a non-breaking space in a paragraph is to preserve
correct HTML - as I recall, it is an error to have consecutive empty
paragraphs.

(Netscape Composer, and Mozilla Composer, have the same kind of behaviour.
Sigh.)

Charles McCN

On Fri, 12 Jan 2001, Tina Marie Holmboe wrote:

  On Thu, Jan 11, 2001 at 06:57:22PM -0600, Jim Thatcher wrote:

  > The request was for "specific" examples. I would like to see those too.

    I've actually manage to get my boss to give me a FP 2000 to play with,
   so lets see what we can find.

     * Test #1. Write a little bit of text, and click the 'increase indent'
       button twice.

       <blockquote>
         <blockquote>
          <p>This is a test</p>
         </blockquote>
       </blockquote>

       Folks, BLOCKQUOTE still does not produce 'indentation', even if some
       notious UAs do. It *might* - in a smart screen-reader - produce something
       aking to " bla, bla, bla, and I quote <insert content of blockquote> ";
       which would be *ehem* so cool. No, it isn't incorrect HTML, but it sure
       isn't a good practice.

     * Test #2. Lets press CR a few times.

  <p>&nbsp;</p>

  <p>&nbsp;</p>

  <p>&nbsp;</p>

  <p>&nbsp;</p>

  <p>&nbsp;</p>

       Ehm. Well. Um. Why ?


    ... and it sets the default charset of new documents to windows-1252. Why
    not iso-8859-1 or unicode ?

    Ok, so far I've not found any *HTML errors*, but some of these things may
    just present accessibility difficulties IMHO.



-- 
Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
until 6 January 2001 at:
W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France
Received on Friday, 12 January 2001 17:33:21 GMT

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