Return-Path: 
 <docs-dev-return-145-apmail-perl-docs-dev-archive=perl.apache.org@perl.apache.org>
Delivered-To: apmail-perl-docs-dev-archive@perl.apache.org
Received: (qmail 485 invoked by uid 500); 4 Jan 2002 21:40:40 -0000
Mailing-List: contact docs-dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:docs-dev@perl.apache.org>
List-Help: <mailto:docs-dev-help@perl.apache.org>
List-Unsubscribe: <mailto:docs-dev-unsubscribe@perl.apache.org>
List-Subscribe: <mailto:docs-dev-subscribe@perl.apache.org>
Delivered-To: mailing list docs-dev@perl.apache.org
Received: (qmail 474 invoked from network); 4 Jan 2002 21:40:39 -0000
X-Authentication-Warning: mail.zsi.at: Host
 chello213047065059.11.univie.teleweb.at [213.47.65.59] claimed to be
 o2001.marx
Date: Fri, 4 Jan 2002 22:42:24 +0100
To: docs-dev@perl.apache.org
Subject: table or not table
Message-ID: <20020104224224.K740@zsi.at>
Mail-Followup-To: docs-dev@perl.apache.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
From: Thomas Klausner <domm@zsi.at>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi!

As the implementation of a basic table around the left nav / content area is
rather trivial, I'd like to discuss the issue once more:

PROs of using table:
* The page renders as intended on non-CSS browser

CONs of using table:
* The page won't render before </table> is transmitted to the client
* Some browsers (lynx, browsers for disabled people) don't render tables
* the Web Content Accessibility Guidelines 1.0 disencourage the usage of
HTML for presentation.
(http://www.w3.org/TR/WCAG10/#gl-structure-presentation
Misusing markup for a presentation effect (e.g., using a table for layout or
a header to change the font size) makes it difficult for users with
specialized software to understand the organization of the page or to
navigate through it.
)

PROs of not using table:
* The page degrades properly on all browser (exept buggy ones)
* Less HTML overhead (although very minor in this case, but quite big when
compared to Stas' initial design)

CONs of not using tables:
* The page may look bad on browsers with no or buggy CSS support


So the main thing to decide is:
Do we want the page look exactly (or nearly) the same on all browsers
thereby using some (IMO) dirty HTML tricks, or do we want the page to be
clean and well degrading, but looking broken/strange on some (buggy) browsers.

I think you know my opinion (don't use the table) but if this is a little bit
too utopian for the mod_perl site, I won't object to using a table.
(Although I don't like giving in to "the mainstream" just because
"if everybody does it wrong, why should I care". If enough people do care
and communicate this issue, sooner or later web pages will be working for
everyone (no more "please enable JS/download flash/take this cookie"
bouncers anymore!!)

But I won't let my personal crusade get in the way of the mod_perl
community, so I don't insist on my ideas.

Maybe we should discuss this issue on the mod_perl mailing list?


-- 
 D_OMM      +---->  http://domm.zsi.at <-----+
 O_xyderkes |       neu:  Arbeitsplatz       |   
 M_echanen  | http://domm.zsi.at/d/d162.html |
 M_asteuei  +--------------------------------+



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org