This is Interesting: Free Magazines for Graphics designers and webmasters  


Home > Archive > Site Ratings & Reviews > December 2003 > killer reason for not using tables?





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author killer reason for not using tables?
Michael Hughes

2003-12-03, 7:25 pm

Hi All,

I've become part of a team to redevelop
a major coporate website. I find myself
alone argueing for not using tables. I've
tried all the usual reasons that people list
here, to no avail. It's too late now to change
the direction of this project, but for the future,
so I'm better prepared, I'm looking for that one,
simple killer reason I can give to make the
case for not using them. Something fairly simple
that the non html-writing management will also understand
too would help.

Also, what do people think about Javascript drop
down menus on sites?

Regards

Michael.
Bonnie Granat

2003-12-03, 7:25 pm


"Michael Hughes" <michael@entamedia.com> wrote in message
news:a094c608.0311050047.144b33e1@posting.google.com...
quote:

> Hi All,
>
> I've become part of a team to redevelop
> a major coporate website. I find myself
> alone argueing for not using tables. I've
> tried all the usual reasons that people list
> here, to no avail. It's too late now to change
> the direction of this project, but for the future,
> so I'm better prepared, I'm looking for that one,
> simple killer reason I can give to make the
> case for not using them. Something fairly simple
> that the non html-writing management will also understand
> too would help.
>
> Also, what do people think about Javascript drop
> down menus on sites?
>



STAM = Saves time and money

Coding time goes down. People can do other things.
Server space needs reduced. All those table tags take up real estate and
cost money.


--
Bonnie Granat
Granat Technical Editing and Writing
http://www.granatedit.com

West

2003-12-03, 7:26 pm

"Michael Hughes" <michael@entamedia.com> wrote in message
news:a094c608.0311050047.144b33e1@posting.google.com...
quote:

> Hi All,
>
> I've become part of a team to redevelop
> a major coporate website. I find myself
> alone argueing for not using tables. I've
> tried all the usual reasons that people list
> here, to no avail. It's too late now to change
> the direction of this project, but for the future,
> so I'm better prepared, I'm looking for that one,
> simple killer reason I can give to make the
> case for not using them. Something fairly simple
> that the non html-writing management will also understand
> too would help.




There is no "killer reason" !!
....unless you think in terms of accessibility for disabled persons and those
viewing the net on devices other than a PC/MAC


--
W

quote:

>
> Also, what do people think about Javascript drop
> down menus on sites?
>
> Regards
>
> Michael.




rf

2003-12-03, 7:26 pm


"Michael Hughes" <michael@entamedia.com> wrote in message
news:a094c608.0311050047.144b33e1@posting.google.com...
quote:

> Hi All,


quote:

> Also, what do people think about Javascript drop
> down menus on sites?



They are are a bloody pain in the arse. An advanced case of mystery meat
navigation:
http://webpagesthatsuck.com/

Cheers
Richard.


jake

2003-12-03, 7:26 pm

In message <if3qb.4329$bD.16613@news.indigo.ie>, West <not@this.one>
writes
quote:

>"Michael Hughes" <michael@entamedia.com> wrote in message
>news:a094c608.0311050047.144b33e1@posting.google.com...
>
>
>There is no "killer reason" !!
>...unless you think in terms of accessibility for disabled persons



Not really an issue, providing the content linearizes correctly. In
practice, it's rare to come across a tables-based site that doesn't
work.
quote:

> and those
>viewing the net on devices other than a PC/MAC
>


True. Maybe he just doesn't care about the 0.00000001% of the population
who use their cell phones ;-)
quote:

>
>--
>W
>
>
>
>



--
Jake
kchayka

2003-12-03, 7:26 pm

Michael Hughes wrote:
quote:

> Hi All,
>
> I've become part of a team to redevelop
> a major coporate website. I find myself
> alone argueing for not using tables. I've
> tried all the usual reasons that people list
> here, to no avail. It's too late now to change
> the direction of this project, but for the future,
> so I'm better prepared, I'm looking for that one,
> simple killer reason I can give to make the
> case for not using them. Something fairly simple
> that the non html-writing management will also understand
> too would help.



Not that I think espn.com's redesign is good (it isn't), but they did
quote some impressive figures on bandwidth savings.
<URL:http://devedge.netscape.com/viewsou...n-interview/01/>
quote:

> Also, what do people think about Javascript drop
> down menus on sites?



In general, they create usability and/or accessibility problems. The
more submenu levels there are, the worse they are. If you use these
things, make sure you at least have a site map accessible from a plain
text link on every page. Not every page needs to be listed on the site
map, but every page does need to be accessible with JavaScript disabled.

--
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
Nico Schuyt

2003-12-03, 7:26 pm

Bonnie Granat wrote:
quote:

> "Michael Hughes" wrote


quote:

[QUOTE][color=darkred]
> STAM = Saves time and money
> Coding time goes down. People can do other things.
> Server space needs reduced. All those table tags take up real estate
> and cost money.



Well, designing in CSS/div boxes can be quite expensive too :-)
Nico
(How much money did you spent on developing http://www.granatedit.com?)



Safalra

2003-12-03, 7:26 pm

"West" <not@this.one> wrote in message news:<if3qb.4329$bD.16613@news.indigo.ie>...
quote:

> "Michael Hughes" <michael@entamedia.com> wrote in message
> news:a094c608.0311050047.144b33e1@posting.google.com...
>
> There is no "killer reason" !!
> ...unless you think in terms of accessibility for disabled persons and those
> viewing the net on devices other than a PC/MAC



So there's the killer reason: use tables and lose customers. Nothing
gets a company to act like the phrase 'lose customers'.

--- Stephen Morley ---
http://www.safalra.com
West

2003-12-03, 7:26 pm


"Safalra" <usenet@safalra.com> wrote in message
news:c555467b.0311050832.4931699f@posting.google.com...
quote:

> "West" <not@this.one> wrote in message


news:<if3qb.4329$bD.16613@news.indigo.ie>...
quote:

those[QUOTE][color=darkred]
>
> So there's the killer reason: use tables and lose customers. Nothing
> gets a company to act like the phrase 'lose customers'.
>



You wrote "use tables and lose customers"
....how do you figure that one?

--
W
quote:

> --- Stephen Morley ---
> http://www.safalra.com




Mark Parnell

2003-12-03, 7:26 pm

Sometime around 5 Nov 2003 00:47:38 -0800, Michael Hughes is reported to
have stated:
quote:

> Hi All,



G'day.
quote:

>
> I'm looking for that one,
> simple killer reason I can give to make the
> case for not using them. Something fairly simple
> that the non html-writing management will also understand
> too would help.



Unfortunately there isn't "one, simple killer reason". But there are
various reasons, which when combined are fairly powerful (IMHO). The main
ones (that I can think of off the top of my head):

o Reduced code = better search engine visibility/rankings = more sales =
better profit margin
o Reduced code = smaller file sizes = lower bandwidth costs = better profit
margin
o Reduced code = smaller file sizes = faster page loading times = better
user experience = more sales = better profit margin
o The ability to change the design of the entire site in one file, rather
than having to go through every file. This means more time to do [insert
other more important things here].
o Site will generally be more accessible to users with disabilities (don't
know about where you are, but here in Australia that is required by
legislation).

--
Mark Parnell
http://www.clarkecomputers.com.au
Safalra

2003-12-03, 7:26 pm

"West" <not@this.one> wrote in message news:<aucqb.4448$bD.16868@news.indigo.ie>...
quote:

> "Safalra" <usenet@safalra.com> wrote in message
> news:c555467b.0311050832.4931699f@posting.google.com...
> news:<if3qb.4329$bD.16613@news.indigo.ie>...
> those
>
> You wrote "use tables and lose customers"
> ...how do you figure that one?



If 'disabled' people can't use your site, they'll find it a bit
difficult to purchase your products. We seem to be going round in
circles here...

--- Stephen Morley ---
http://www.safalra.com
jake

2003-12-03, 7:26 pm

In message <c555467b.0311060811.7c387769@posting.google.com>, Safalra
<usenet@safalra.com> writes
quote:

>"West" <not@this.one> wrote in message
>news:<aucqb.4448$bD.16868@news.indigo.ie>...
>
>If 'disabled' people can't use your site, they'll find it a bit
>difficult to purchase your products.




[snip]

Interesting, but in what way does a table-based layout prevent them from
using the site? (Assuming that the table linearizes correctly).

regards.

--
Jake
picayunish

2003-12-03, 7:26 pm

Safalra wrote in news:c555467b.0311060811.7c387769@posting.google.com:
quote:

> "West" <not@this.one> wrote in message
> news:<aucqb.4448$bD.16868@news.indigo.ie>...
>
> If 'disabled' people can't use your site, they'll find it a bit
> difficult to purchase your products.



Hmmm.
Disabling tables. I thought you can only disabling JS and Cookies with the
browsers.
Where can I find those browsers, that can disabling tables.
--
Edwin van der Vaart
http://www.semi-conductor.nl/ Links to Semiconductors sites
http://members.chello.nl/e.vandervaart/ Experimental site


rf

2003-12-03, 7:26 pm


"picayunish" <e_vdvaart@yahoo.co.uk> wrote in message
news:M2zqb.1680$%W3.7045@amstwist00...
quote:

> Safalra wrote in news:c555467b.0311060811.7c387769@posting.google.com:
and[QUOTE][color=darkred]
>
> Hmmm.
> Disabling tables. I thought you can only disabling JS and Cookies with the
> browsers.
> Where can I find those browsers, that can disabling tables.



Any text to speach browser.

They don't do tables. They don't do images. They totally screw up frames or
rather frames totally screw *them* up. They only read the content. If the
tables do not linearise correctly then you get jumbled content.

Cheers
Richard.


Nico Schuyt

2003-12-03, 7:26 pm

picayunish wrote:
quote:

>
> Hmmm.
> Disabling tables. I thought you can only disabling JS and Cookies
> with the browsers.
> Where can I find those browsers, that can disabling tables.



In the discussion not the tables are disabled but the visitor.
Nico


William Tasso

2003-12-03, 7:26 pm

picayunish wrote:
quote:

> ...
> Where can I find those browsers, that can disabling tables.



Lynx

--
William Tasso - http://WilliamTasso.com


kchayka

2003-12-03, 7:26 pm

William Tasso wrote:
quote:

> picayunish wrote:
>
> Lynx



And Links

--
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
Mark Parnell

2003-12-03, 7:26 pm

Sometime around Thu, 6 Nov 2003 22:42:08 +0100, Nico Schuyt is reported to
have stated:
quote:

>
> In the discussion not the tables are disabled but the visitor.



<nitpick mode="political_correctness">The visitor _has_a_disability_. They
are not disabled.</nitpick> :-)

--
Mark Parnell
http://www.clarkecomputers.com.au
Alexander Weber

2003-12-03, 7:26 pm

"William Tasso" <news27@tbdata.com> wrote:
quote:

>picayunish wrote:
>
>Lynx



My Lynx shows tables. The table cells are lined up under each other.
If you use simple table layouts (no nested tables) I don't see a
difference to a CSS layout where the elements (e.g., <div> ) are also
printed under each other (in a text browser).

Alex.
jake

2003-12-03, 7:26 pm

In message <Kazqb.181432$bo1.178050@news-server.bigpond.net.au>, rf
<making.it.up@the.time> writes
quote:

>
>"picayunish" <e_vdvaart@yahoo.co.uk> wrote in message
>news:M2zqb.1680$%W3.7045@amstwist00...
>and
>
>Any text to speach browser.
>
>They don't do tables. They don't do images. They totally screw up frames or
>rather frames totally screw *them* up. They only read the content. If the
>tables do not linearise correctly then you get jumbled content.
>
>Cheers
>Richard.
>
>


I may have got this wrong, but are you saying that
screen-readers/voice-browsers (i.e. 'assistive technology') can't handle
tables, images, and frames?

regards.

--
Jake
William Tasso

2003-12-03, 7:26 pm

Alexander Weber wrote:
quote:

> "William Tasso" <news27@tbdata.com> wrote:
>
>
> My Lynx shows tables. The table cells are lined up under each other.



Really? Mine doesn't. Perhaps it is markup dependent - do you have a url?

--
William Tasso - http://WilliamTasso.com


kchayka

2003-12-03, 7:26 pm

William Tasso wrote:
quote:

> Alexander Weber wrote:
>
> Really? Mine doesn't. Perhaps it is markup dependent - do you have a url?



I think it depends on how much content is in a cell. It does try to
line up columns when possible, but if there is enough content in a cell
to cause line-wrapping, Lynx will probably linearize the table, or at
least that cell/row. It can get messy if the table has a mix of short
and long cell content.

Links, however, has an option to specifically disable table support.
BTW, Links has become my browser of choice on Linux. I think it's a
better text browser than Lynx, and I'm even starting to like it better
than most graphical browsers. :)

--
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
William Tasso

2003-12-03, 7:26 pm

kchayka wrote:
quote:

> ...
> Links, however, has an option to specifically disable table support.
> BTW, Links has become my browser of choice on Linux.



Would you know if there's a windows version - no *nix workstations here.
quote:

> I think it's a
> better text browser than Lynx, and I'm even starting to like it better
> than most graphical browsers. :)



that's some recommendation - I'll have to take a peek

--
William Tasso - http://WilliamTasso.com


Mark Parnell

2003-12-03, 7:26 pm

Sometime around Fri, 7 Nov 2003 00:14:12 -0000, William Tasso is reported
to have stated:
quote:

> kchayka wrote:
>
> Would you know if there's a windows version - no *nix workstations here.



I've got it running on Win2k. Not sure where I downloaded it from, though.

--
Mark Parnell
http://www.clarkecomputers.com.au
Toby A Inkster

2003-12-03, 7:26 pm

picayunish wrote:
quote:

> Where can I find those browsers, that can disabling tables.



Opera 6.1 had a "disable tables" option in preferences. This was removed
for Opera 7.0x and 7.1x, but Opera 7.2x comes with a "Disable Tables"
user stylesheet, which goes a little something like this...

==================================================================
@charset "UTF-8";
/*
Name: Disable tables
Version: 1.01
Author: Opera Software ASA
Description: This style sheet disables tables.

Copyright © 2003 Opera Software ASA.
*/

table, caption, tr, thead, tfoot, tbody, th, td {
display: block !important;
float: none !important;
max-width: none !important;
min-width: 0px !important;
width: auto !important;
max-height: none !important;
min-height: 0px !important;
height: auto !important;
/* text-align: left !important;*/
}

thead, th {font-weight: bolder !important;}
==================================================================

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

Toby A Inkster

2003-12-03, 7:26 pm

Alexander Weber wrote:
quote:

> My Lynx shows tables.



Yes, recent versions kinda sorta can, as long as you don't play with
colspan, rowspan, etc, and as long as the data in each cell is short...
there are a lot of "if"s involved.

Older versions used to implement </td><td> as a space and </tr><tr> as a
new line.

Links is even better than Lynx. It can handle more complex tables and
FRAMES!

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

rf

2003-12-03, 7:26 pm


"jake" <jake@gododdin.demon.co.uk> wrote in message
news:DvIaphG7gtq$EwGG@gododdin.demon.co.uk...
quote:

> In message <Kazqb.181432$bo1.178050@news-server.bigpond.net.au>, rf
> <making.it.up@the.time> writes
the[QUOTE][color=darkred]
or[QUOTE][color=darkred]
> I may have got this wrong, but are you saying that
> screen-readers/voice-browsers (i.e. 'assistive technology') can't handle
> tables, images, and frames?



Yes, I am, in many cases. The worse the authoring the worse the support.

Lets take them individually.

Tables.

I construct a two column table to contain two columns of text. I put these
columns in two different cells. 4 cells all up. The text is supposed to be
read top to bottom, like a newspaper.

Sentence 1 Sentence 3
Sentence 2 Sentence 4

A visual browser will display this correctly. An aural browser will read:
<quote>
Sentence 1
Sentence 3
Sentence 2
Sentence 4
</quote.

This is an example of a table not linearising correctly. The content is
there, it just does not mean anything.

Images.

An aural browser can not display an image. It has no screen, just a
loudspeaker. The aural browser will read the contents of the alt attribute
the author has thoughtfully provided, and just how often is that *not*
provided. No alt text and the browser reads:
<quote>
images slash roo dot jpeg
</quote>

Frames, the worst case of all.

Download a copy of lynx, it's a free text only browser. It gives you a good
idea of how a page will sound when read by an aural browser.

I fired up lynx and found a random framed web site. This is what lynx
displayed:

<quote>
FRAME: top
FRAME: contents
FRAME: main
FRAME: right
FRAME: bottom

This page uses frames, but your browser doesn't support them.
</quote>

When I navigate to one of these frames I can not go back to the frameset
because there is no like from the frame back to the frameset.

Not very user friendly, is it.

Cheers
Richard.


kchayka

2003-12-03, 7:26 pm

Toby A Inkster wrote:
quote:

>
> Links is even better than Lynx. It can handle more complex tables and
> FRAMES!



Yeah and images and JavaScript and...

Links is best when all that stuff is disabled. :)

--
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
Mark Parnell

2003-12-03, 7:26 pm

Sometime around Fri, 07 Nov 2003 01:02:13 GMT, rf is reported to have
stated:
quote:

>
> I construct a two column table to contain two columns of text. I put these
> columns in two different cells. 4 cells all up. The text is supposed to be
> read top to bottom, like a newspaper.
>
> Sentence 1 Sentence 3
> Sentence 2 Sentence 4
>
> A visual browser will display this correctly. An aural browser will read:
> <quote>
> Sentence 1
> Sentence 3
> Sentence 2
> Sentence 4
> </quote.
>
> This is an example of a table not linearising correctly. The content is
> there, it just does not mean anything.



One of the reasons, of course, for not using tables for layout. If those 2
columns were divs, then the text browser would linearise them correctly.
:-)

--
Mark Parnell
http://www.clarkecomputers.com.au
kchayka

2003-12-03, 7:26 pm

William Tasso wrote:
quote:

> kchayka wrote:
>
> Would you know if there's a windows version - no *nix workstations here.



<URL:http://artax.karlin.mff.cuni.cz/~mikulas/links/>

Windows version is still beta, I haven't tried it yet.

--
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
Alexander Weber

2003-12-03, 7:26 pm

"rf" <making.it.up@the.time> wrote:
quote:

>I construct a two column table to contain two columns of text. I put these
>columns in two different cells. 4 cells all up. The text is supposed to be
>read top to bottom, like a newspaper.
>
>Sentence 1 Sentence 3
>Sentence 2 Sentence 4
>
>A visual browser will display this correctly. An aural browser will read:
><quote>
>Sentence 1
>Sentence 3
>Sentence 2
>Sentence 4
></quote.
>
>This is an example of a table not linearising correctly. The content is
>there, it just does not mean anything.



Is this not only an example of bad table coding? If you had used e.g.
only two cells in one row you wouldn't have had a problem with the
aural (or text) browser.

On the other hand, I could give you an example of bad CSS coding as
well:

code:
<div class="A">Sentence 1</div>
<div class="B">Sentence 3</div>
<div class="C">Sentence 2</div>
<div class="D">Sentence 4</div>

with a corresponding style-sheet (defining positition:absolute for the
different classes), a "normal" visual browser would show the "correct"
content:
Sentence 1 Sentence 3
Sentence 2 Sentence 4

But an aural/text browser will read:
Sentence 1
Sentence 3
Sentence 2
Sentence 4
.... which is not what we want.

What I want to say is, that many people claim, as in this thread, that
tables are evil per se and cannot be displayed correctly by aural/text
browsers. But I don't see a problem if tables are used carefully. If
you use tables in "the wrong way" (as your example above) of course
they cause troubles, as any other html flaws. But what is wrong when
using simple, well considered table structures?

There comes again the question about the killer reason against tables
from the OP.

Btw., I don't like tables neither. But I think its more for esthetic
reasons. And that's not a killer reason IMHO. That's why I would also
be interested in _good_ arguments against tables.

Alex.
Eric Bohlman

2003-12-03, 7:26 pm

Mark Parnell <webmaster@clarkecomputers.com.au> wrote in
news:82vmp1canwvz.1hmxtbmd5yxtv.dlg@40tude.net:
quote:

> Sometime around Thu, 6 Nov 2003 22:42:08 +0100, Nico Schuyt is
> reported to have stated:
>
> <nitpick mode="political_correctness">The visitor _has_a_disability_.
> They are not disabled.</nitpick> :-)



There's actually a legal reason why disability-rights laws like the
Americans with Disabilities Act refer to "persons with disabilities" rather
than "disabled persons": the latter is what lawyers call a "term of art"
which means that it has a very specific meaning in law, a meaning that
doesn't correspond to its vernacular meaning. In particular, "disabled
person" is a term of art for a person who is entitled to certain financial
benefits (either public or from private insurance) as a result of medical
problems making him unable to earn more than a certain amount of income.
Since disability-rights laws primarily deal with people who don't meet that
definition, they have to use a different term. Otherwise courts would
interpret the laws as applying only to people who qualified for benefits,
which in the case of things like employment discrimination would lead to
all sorts of nonsense.

As it turns out, the popular conception of "disabled person" somewhat
resembles the legal term of art, so I don't think it's quite fair to refer
to the distinction as mere "political correctness"; it's more a matter of
precision in language. There are lots of people who have disabilities, but
would consider "being disabled" to be something else entirely. The latter
sounds to me as if it's implying something a lot more pervasive than the
former. It comes off as what Gordon Allport, in his classic _The Nature of
Prejudice_, called a "label of primary potency"; a characteristic that's
taken to be the *defining* characteristic of a person or a thing. And such
labels can have unintended effects, even though they're usually well-meant.

("Joe Blow is 26 years old. He lives in Seattle, is married with one
child, plays bass in a local punk band, and works as a programmer for
Microsoft." For some people, the overriding impression they'd get from
that is "agent of the Evil Empire." That's an illustration of a label of
primary potency at work.)

Eric Bohlman

2003-12-03, 7:26 pm

"rf" <making.it.up@the.time> wrote in
news:paCqb.50$aT.46@news-server.bigpond.net.au:
quote:

> I construct a two column table to contain two columns of text. I put
> these columns in two different cells. 4 cells all up. The text is
> supposed to be read top to bottom, like a newspaper.
>
> Sentence 1 Sentence 3
> Sentence 2 Sentence 4
>
> A visual browser will display this correctly. An aural browser will
> read: <quote>
> Sentence 1
> Sentence 3
> Sentence 2
> Sentence 4
> </quote.
>
> This is an example of a table not linearising correctly. The content
> is there, it just does not mean anything.



You can see some (often quite amusing) examples of failed linearization of
multi-column text by looking at Google's summaries of PDF pages. My two
favorites are:

"... 2 diabetes, it must Please forward address changes or be remembered
that glucose
intolerance occurs as part of a complex meta- subscription request to Todd
Chin ..."

and

"[PDF]Temperature Sensor Eludes Analog Interfacing
File Format: PDF/Adobe Acrobat - View as HTML
.... Two 74HC595 serial-to-parallel converters will directly drive seven-
segment
digits to Dallas Semiconductor Corp. 4401 South Beltwood Pkwy. ...
www.circuitcellar.com/library/print/ hcs-pdf/42-Bachiochi.pdf - Similar
pages"


Toby A Inkster

2003-12-03, 7:26 pm

Mark Parnell wrote:
quote:

> Sometime around Fri, 7 Nov 2003 00:14:12 -0000, William Tasso is reported
> to have stated:
>
>
> I've got it running on Win2k.



Does the Windows version support the mouse? (I can't imagine the mouse
working properly in a DOS box.)

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

rf

2003-12-03, 7:26 pm


"Toby A Inkster" <UseTheAddressInMySig@deadspam.com> wrote in message
news:pan.2003.11.07.08.02.45.311737@goddamn.co.uk...
quote:

> Mark Parnell wrote:
>
> Does the Windows version support the mouse? (I can't imagine the mouse
> working properly in a DOS box.)



Mice work quite well in a DOS box, providing the correct dos mode drivers
are installed.

In fact, mice were invented before Windows.

Cheers
Richard.


jake

2003-12-03, 7:26 pm

In message <paCqb.50$aT.46@news-server.bigpond.net.au>, rf
<making.it.up@the.time> writes
quote:

>
>"jake" <jake@gododdin.demon.co.uk> wrote in message
>news:DvIaphG7gtq$EwGG@gododdin.demon.co.uk...
>the
>or
>
>Yes, I am, in many cases. The worse the authoring the worse the support.



I think the key word here is 'authoring'.
quote:

>
>Lets take them individually.
>
>Tables.
>
>I construct a two column table to contain two columns of text. I put these
>columns in two different cells. 4 cells all up. The text is supposed to be
>read top to bottom, like a newspaper.
>
>Sentence 1 Sentence 3
>Sentence 2 Sentence 4
>
>A visual browser will display this correctly. An aural browser will read:
><quote>
>Sentence 1
>Sentence 3
>Sentence 2
>Sentence 4
></quote.
>
>This is an example of a table not linearising correctly. The content is
>there, it just does not mean anything.



This would only happen if the table is authored to linearise
incorrectly, but in practice this rarely happens. The author would
usually put these 4 sentences into 2 cells so that the browser will
speak:
Sentence 1, 2, followed by 3 and 4.

So, I think we can forget about tables being a problem (that's a problem
with authoring -- not with tables as such)..
quote:

>
>Images.
>
>An aural browser can not display an image. It has no screen, just a
>loudspeaker. The aural browser will read the contents of the alt attribute
>the author has thoughtfully provided, and just how often is that *not*
>provided. No alt text and the browser reads:
><quote>
>images slash roo dot jpeg
></quote>



Again, this is an authoring problem. Providing that correct use is made
of ALT, LONGDESC and D-link I don't think that we have a problem here
either.
quote:

>
>Frames, the worst case of all.
>
>Download a copy of lynx, it's a free text only browser. It gives you a good
>idea of how a page will sound when read by an aural browser.
>
>I fired up lynx and found a random framed web site. This is what lynx
>displayed:
>
><quote>
> FRAME: top
> FRAME: contents
> FRAME: main
> FRAME: right
> FRAME: bottom
>
> This page uses frames, but your browser doesn't support them.
></quote>
>
>When I navigate to one of these frames I can not go back to the frameset
>because there is no like from the frame back to the frameset.
>
>Not very user friendly, is it.



Nope; not at all friendly. However, using a real
screen-reader/voice-browser with a framed site is a somewhat different
experience.

Let's say I visit the most common form of framed site (you know -- logo
in one, navigation in another, main content in the third).

The first thing I hear is: 'Frame 1 of 3: Navigation' ...... followed by
the list of links. The procedure from here is to just 'toggle' between
the frames (typically ctrl/tab) to read the frame I want to. So -- not
really a problem (especially if the author has thoughtfully put a
<title> on each page so that I know what it's for).

Admittedly, there are one or two 'horror sites' that I've come across
with up to 15 (yes, *fifteen*) frames in use, but mercifully these are
very much a rarity.

Authoring with disabilities in mind is really the key.

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

To go back to the original poster's question, I'd have to have to say
that for the next year or two (or three) there really *isn't* a 'killer
reason' for not using tables for layout -- provided they linearise
correctly and they are not deeply nested.

regards.
quote:

>
>Cheers
>Richard.
>
>



--
Jake
kchayka

2003-12-03, 7:27 pm

Alexander Weber wrote:
quote:

>
> What I want to say is, that many people claim, as in this thread, that
> tables are evil per se and cannot be displayed correctly by aural/text
> browsers. But I don't see a problem if tables are used carefully.



While a well-constructed layout table may not pose serious issues for
aural/text browsers, they certainly can for some devices. Table layouts
usually do quite poorly on the small screens of mobile devices, whereas
CSS layouts can do quite well, especially with well-formed, structured
markup that degrades nicely when CSS is disabled.

--
To email a reply, remove (dash)un(dash). Mail sent to the un
address is considered spam and automatically deleted.
West

2003-12-03, 7:27 pm


"kchayka" <kcha-un-yka@sihope.com> wrote in message
news:3fab95fc$0$43848$39cecf19@news.twtelecom.net...
quote:

> Alexander Weber wrote:
>
> While a well-constructed layout table may not pose serious issues for
> aural/text browsers, they certainly can for some devices. Table layouts
> usually do quite poorly on the small screens of mobile devices, whereas
> CSS layouts can do quite well, especially with well-formed, structured
> markup that degrades nicely when CSS is disabled.





....geeks and gearheads who use such devices will or should know better.
....this is an inadequacy with the device's display capability.

So, what do have at the end of this thread :-
1. Tables do not pose serious issues for aural/text browsers?
2. Tables 'may' present a problem for the tiny % of mobile device users?

Seems to me as if a combination of tables and css is ok !!

--
W





quote:

>
> --
> To email a reply, remove (dash)un(dash). Mail sent to the un
> address is considered spam and automatically deleted.




picayunish

2003-12-03, 7:27 pm

Nico Schuyt wrote in news:3faabfee$0$206$1b62eedf@news.euronet.nl:
quote:

> picayunish wrote:
>
> In the discussion not the tables are disabled but the visitor.



rofl
--
Edwin van der Vaart
http://www.semi-conductor.nl/ Links to Semiconductors sites
http://members.chello.nl/e.vandervaart/ Experimental site


picayunish

2003-12-03, 7:27 pm

kchayka wrote in news:3faad007$0$43850$39cecf19@news.twtelecom.net:
quote:

> William Tasso wrote:
>
>
> And Links



Sorry :-?
--
Edwin van der Vaart
http://www.semi-conductor.nl/ Links to Semiconductors sites
http://members.chello.nl/e.vandervaart/ Experimental site


picayunish

2003-12-03, 7:27 pm

picayunish wrote in news:M2zqb.1680$%W3.7045@amstwist00:
quote:

>
> Hmmm.
> Disabling tables. I thought you can only disabling JS and Cookies with
> the browsers.
> Where can I find those browsers, that can disabling tables.



A lot of replies on the subject disabing tables.
Thanx mates, I was forgotten about the text-browsers.

What's next. Disabling webpages in the browsers ?
--
Edwin van der Vaart
http://www.semi-conductor.nl/ Links to Semiconductors sites
http://members.chello.nl/e.vandervaart/ Experimental site


Toby A Inkster

2003-12-03, 7:27 pm

rf wrote:
quote:

> "Toby A Inkster" <UseTheAddressInMySig@deadspam.com> wrote in message
> news:pan.2003.11.07.08.02.45.311737@goddamn.co.uk...
>
> Mice work quite well in a DOS box, providing the correct dos mode drivers
> are installed.
>
> In fact, mice were invented before Windows.



Well, yes I know mice work fine in proper DOS -- I used to use a trackball
with DOS 6 point something. I was just wondering how well it worked in a
Windows DOS box -- I've never seen mousey stuff work in them (except that
crappy copy and paste thing).

(For that matter, I am also outstanded at how well it works with terminal
emulators on *nix.)

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

Toby A Inkster

2003-12-03, 7:27 pm

West wrote:
quote:

> So, what do have at the end of this thread :-
> 1. Tables do not pose serious issues for aural/text browsers?[1]
> 2. Tables 'may' present a problem for the tiny % of mobile device users?



Also:

3. Table-based layouts tend to result in larger file sizes. If you use CSS
it is true that you have an extra file to download, but once this has been
downloaded it can be cached for use on the next page.

4. Many browsers wait to download "</table>" before even beginning to
render the table. This can cause delays in rendering pages.

5. With a CSS-based layout you can move a navigation column from the left
to the right and back again on a whim -- just by editing a few lines in a
single CSS file. With table-based layouts it requires restructuring each
page.

6. Tables for layout hinders the take-up of the semantic web.

7. Every time you use a table for layout a puppy dies.

[1] Table-based layouts *may* pose serious problems for browsers that do
not support tables. It depends on the layout and the browser.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

Eric Bohlman

2003-12-03, 7:27 pm

Toby A Inkster <UseTheAddressInMySig@deadspam.com> wrote in
news:pan.2003.11.08.00.38.06.69903@goddamn.co.uk:
quote:

> West wrote:
>
>
> Also:
>
> 3. Table-based layouts tend to result in larger file sizes. If you use
> CSS it is true that you have an extra file to download, but once this
> has been downloaded it can be cached for use on the next page.
>
> 4. Many browsers wait to download "</table>" before even beginning to
> render the table. This can cause delays in rendering pages.
>
> 5. With a CSS-based layout you can move a navigation column from the
> left to the right and back again on a whim -- just by editing a few
> lines in a single CSS file. With table-based layouts it requires
> restructuring each page.
>
> 6. Tables for layout hinders the take-up of the semantic web.
>
> 7. Every time you use a table for layout a puppy dies.



8. If tables were used exclusively for tabular data, browser developers,
particularly developers of auditory browsers, would be able to make
browsers treat tables in ways that would be highly appropriate for tabular
data, such as being able to lock headings in place while scrolling (for
visual browsers) or being able to hear the heading corresponding to any
row/column (for auditory browsers). The features could extend to the point
of providing a true spreadsheet-like interface to tables, complete with
column sorting and the like.
Bonnie Granat

2003-12-03, 7:27 pm


"Nico Schuyt" <nschuyt@hotmail.com> wrote in message
news:3fa906b7$0$201$1b62eedf@news.euronet.nl...
quote:

> Bonnie Granat wrote:
>
>
>
> Well, designing in CSS/div boxes can be quite expensive too :-)
> Nico
> (How much money did you spent on developing http://www.granatedit.com?)
>
>
>



You know, I thought about that as I was writing, but decided that it was
true, anyway.


--
--
Bonnie Granat
http://www.granatedit.com

Toby A Inkster

2003-12-03, 7:27 pm

Eric Bohlman wrote:
quote:

> 8. If tables were used exclusively for tabular data, browser developers,
> particularly developers of auditory browsers, would be able to make
> browsers treat tables in ways that would be highly appropriate for tabular
> data



Great minds think alike:
http://groups.google.com/groups?sel...40goddamn.co.uk
(point 3)

Or should that be "two fools with only one mind"?

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

William Tasso

2003-12-03, 7:27 pm

picayunish wrote:
quote:

> picayunish wrote in news:M2zqb.1680$%W3.7045@amstwist00:
>
> A lot of replies on the subject disabing tables.
> Thanx mates, I was forgotten about the text-browsers.
>
> What's next. Disabling webpages in the browsers ?



a browser that only displays valid markup would be a usefool tool

--
William Tasso - http://WilliamTasso.com


Nico Schuyt

2003-12-03, 7:27 pm

Bonnie Granat wrote:
quote:

> Nico Schuyt wrote in message
[QUOTE][color=darkred]
[QUOTE][color=darkred]
[QUOTE][color=darkred]
[QUOTE][color=darkred]
> You know, I thought about that as I was writing, but decided that it
> was true, anyway.



Ah well, maybe you're right. Perhaps you can save money in the maintenance
of a CSS/div-based site. On the other hand, I have had far more problems
with making a site with a CSS/div design render acceptably in all kinds of
browsers than with a design based on tables (or frames :-).
Nico



Farlo

2003-12-03, 7:27 pm

"William Tasso" <news27@tbdata.com> wrote:
quote:

> a browser that only displays valid markup would be a usefool tool



A freudian slip? Heehee ...

--
Farlo, the Urban Fey Dragon
Toby A Inkster

2003-12-03, 7:27 pm

William Tasso wrote:
quote:

> a browser that only displays valid markup would be a usefool tool



Serve XHTML as text/xml, application/xml or application/xhtml+xml and you
will be half way there.

All browsers *should* check these MIME types for XML well-formedness and
certainly Opera 6+ and Mozilla 0.9.4+ (and possibly earlier versions of
each!) actually *do* this.

Validating browsers (I don't know of any such browsers) should also check
the page against the DTD and catch other errors such as invalid entities,
illegal nesting (e.g. <table><div><tr><td></td></tr></div></table> ) and so
on and so forth.

However, recent versions of Mozilla will validate against their own
internal DTDs (on my installation these can be found in the directory
"/usr/lib/mozilla-1.4/res/dtd/"). The internal DTDs only contain the
entity definitions, so Mozilla will only spot XML well-formedness
errors and illegal entities, but it's clearly on its way to becoming a
validating parser.

All that having been said, there is suh a beast as a web *server* that
will only serve valid markup. Google for mod_tidy.

--
Toby A Inkster BSc (Hons) ARCS
Contact Me - http://www.goddamn.co.uk/tobyink/?page=132

Mark Parnell

2003-12-03, 7:27 pm

Sometime around Fri, 07 Nov 2003 08:02:46 +0000, Toby A Inkster is reported
to have stated:
[Links]
quote:

>
> Does the Windows version support the mouse? (I can't imagine the mouse
> working properly in a DOS box.)



To a degree, but no, not properly. The scroll wheel works, and you can
select text (then right-click to copy), but that's about it AFAICT. Perhaps
better support on Win9x (have found that with other DOS programs).

--
Mark Parnell
http://www.clarkecomputers.com.au
Sponsored Links


Copyright 2003 - 2008 forum4designers.com  Software forum  Computer Hardware reviews