Gabriele Romanato wrote: > Browser's support is still improving. My opinion is: if we are using > CSS for professional purposes, we should take into account also > obsolete versions. otherwise, we should drop our support to these > browsers.
I have problems understanding practicality here. How does one "drop support"? - by ignoring the existence of an old browser? The result may be really disgraceful, inaccessible, useless in a browser, but if the designer/coder never checks only visitors unfortunate enough to be using that browser will ever know. - by serving it no styles? In practical terms that may not always be so easy, and some of the methods used to prevent a browser from loading/using styles may backfire and affect present and future browsers. On the other hand, if one chooses to take obsolete versions into account and provide a degree of support, where - at which versions, and how, does one draw the lines? I think I have found most answers to the above as it relates to my own work, but it would be interesting to see how others choose or have to deal with obsolete browsers. > see http://transcendingcss.com From that page: "Few visual designers are natural programmers, and as a result, visualizing how to work with markup, CSS and a range of programmatic techniques to create beautiful design is difficult." Well, I am an "art-educated natural programmer" (for lack of a better description), spending time studying the available programmatic techniques so I can sort them out and use what I need when and where I need it. Not very complicated but time-consuming nevertheless, and I seem to find more what I would call obsolete and/or unnecessary limiting techniques and other short-cuts than I find hopelessly obsolete browsers - excluding the _very_ obsolete IE4/NN4 generations from the equation. In too many cases the browsers and their varying degree of standards support seem *not* to be the limiting factor - the designers' urge for control over his/hers own art is. How does one deal with that? Maybe that's what Ingo touched onto by writing... > However, the day the CSS-framework-guys win and produce something > endlessly boring that does not require an understanding of CSS > anymore approaches, so maybe it's time to move on. ...in the post I used to start this thread. Guess both Ingo and I might end up becoming too bored with frameworks and other short-cuts, same as with layout tables ;-) Now, if only designers, developers, coders, whatever would apply their art in ways that lifted and promoted the content instead of competing with it, then "the fine art of web design" might actually be going somewhere regardless of which programmatic techniques, frameworks and other short-cuts was used, and we might see some progress. There's a lot of freedom in CSS based design if one has a deep enough understanding to release it, but the mental, and to some degree the practical, barriers seem to be high. I would like to get a better understanding of these barriers, in order to find more ways around them. regards Georg -- http://www.gunlaug.no ______________________________________________________________________ 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/
