I prefer to use tables for the layout for maximum browser compatibility.
I am not sure how this could work, but what would you think about using CSS ONLY for those effects that CSS is better than basic HTML?
I mean, you can specify a instead of using CSS, or make a table layout instead of elaborating with CSS. Or use only CSS for things like a:hover, or H1 (those XHTML tags that are recurrently found on site) [The use of JavaScript for this is just not practical]
By keeping CSS to a minimum, browsers not supporting CSS can have a more or less good, consistent look. But those visits are arguably inexistent, so it’s not cost-effective (as CSS is much more simpler than direct HTML tagging).
Besides, these methodology helps warranty cross-browser look, because maybe CSS rendering is too relative across browsers.
And finally, I think direct HTML tagging builds a more solid, reliable code than CSS, and warranties a more consistent look.
These is my thought for the CSS naked day. Maybe it’s too much erudition on my part; you’ll tell me “K.I.S.S.: CSS is standard and cheap to code”, but ol’ fashion is sometimes better for me: like prefering printed books to e-books, etc.
Any browser worth worrying about is going to support CSS–and even if it doesn’t, then you get what you see right now, which isn’t so bad (and that’s somewhat what CSS Naked Day is about). CSS can be a pain to learn cross-browser at first, but after you’ve done it for a bit most browser issues aren’t really much of issues at all.
And as far as layouts go, now there’s even a few good frameworks out there that can set up cross-browser ones really quickly (this design uses blueprint).
To Andres. The majority of browsers visiting your site that do not currently support CSS will be doing so for a reason i.e screen readers for users with disabilities or even mobile phone browsers. Tables often give them real issues. XHTML with good mark up on the content and CSS for display is the most sensible option because the info which is important can always be seen wwhilst the design can be appreciated on it’s most suitable platform. See alistapart.com for more info.
I eat food. I listen to music. I sleep. Sometimes. I drink lots of coffee. I make pretty pictures. I talk to people. I believe in things. I write stuff. I take photographs. I have a laughing addiction. I am human. I have more about me over here.
I prefer to use tables for the layout for maximum browser compatibility.
I am not sure how this could work, but what would you think about using CSS ONLY for those effects that CSS is better than basic HTML?
I mean, you can specify a instead of using CSS, or make a table layout instead of elaborating with CSS. Or use only CSS for things like a:hover, or H1 (those XHTML tags that are recurrently found on site) [The use of JavaScript for this is just not practical]
By keeping CSS to a minimum, browsers not supporting CSS can have a more or less good, consistent look. But those visits are arguably inexistent, so it’s not cost-effective (as CSS is much more simpler than direct HTML tagging).
Besides, these methodology helps warranty cross-browser look, because maybe CSS rendering is too relative across browsers.
And finally, I think direct HTML tagging builds a more solid, reliable code than CSS, and warranties a more consistent look.
These is my thought for the CSS naked day. Maybe it’s too much erudition on my part; you’ll tell me “K.I.S.S.: CSS is standard and cheap to code”, but ol’ fashion is sometimes better for me: like prefering printed books to e-books, etc.
Any browser worth worrying about is going to support CSS–and even if it doesn’t, then you get what you see right now, which isn’t so bad (and that’s somewhat what CSS Naked Day is about). CSS can be a pain to learn cross-browser at first, but after you’ve done it for a bit most browser issues aren’t really much of issues at all.
And as far as layouts go, now there’s even a few good frameworks out there that can set up cross-browser ones really quickly (this design uses blueprint).
To Andres. The majority of browsers visiting your site that do not currently support CSS will be doing so for a reason i.e screen readers for users with disabilities or even mobile phone browsers. Tables often give them real issues. XHTML with good mark up on the content and CSS for display is the most sensible option because the info which is important can always be seen wwhilst the design can be appreciated on it’s most suitable platform. See alistapart.com for more info.
David
David: You’re right.