At 08:22 AM 1/17/2009 -0800, Dan Gayle wrote: >Ask a person who uses a screen reader to answer why tables shouldn't >be used for layout. You'll get your answer soon enough.
Pardon my ignorance, but how is it that a CSS layout wouldn't have the same potential issues? >Ask a person who has had to modify or alter a website made in tables, Well, I'm one of those persons, and although, sure, if I want to modify the overall structure of a "tabled" site then I'd probably then have to upload all the HTML files on my site, on the other hand if I'm happy with the structure of my site in the first place (and for the long run), how often would I have to do that? Like, once every five years? Maybe never? >to add new features like a new sidebar You mean like adding in a little table? ;) >or a pull quote within the middle of a block of text. Well, yes, that's exactly the sort of thing that I *would* do (now/already) using CSS -- but I was specifically referring to the overall main layout/structure of a site. >Ask the person using Javascript to add or remove content to their >page without it breaking. I'm not sure what you mean, that is, how that relates to my previous post/thoughts. >The issues with tables are numerous, but you specifically cite the >speed of development. Yes, it might be fast to create the layout. But >it adds tremendous amounts of time trying to modify it later. But what if I don't want to modify it? I've changed the *content* (i.e. text, images) on my sites over the years, but I haven't changed the overall *structure* -- that is, the table that "holds it all together" -- at all. So rather than putting my site together in a way that's not only easier to create in the beginning (and may never have to be changed, because I'm happy with it) and has *no* problems (except, perhaps, for screen readers -- although I confess ignorance about what issues these might have, and how it is that CSS apparently wouldn't have these same issues), you're suggesting that I spend an *extreme* amount of time just getting my site layed out with CSS in the first place, incorporating innumerable hacks and fixes in order to get things to work... only to have to continually update and change those hacks/fixes in forthcoming years as those stupid browser manufactures (et al.) create more (and potentially bigger) problems? I'm not trying to be facetious or anything -- seriously, I genuinely want to understand this. Indeed, I really *would* like to completely transform all my old sites into purely CSS layouts -- but at this point it seems like one has to acquire the equivalent of a PhD in style sheets (like, 10 years of intense education and research) just to do what can already be done, easily and simply and bug-free, with tables. Ron :) Woof?... http://www.Psymon.com Ach, du Leni!... http://www.Riefenstahl.org Hmm... http://www.Imaginary-Friend.ca ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
