"Modern" CSS properties = havoc
Sunday, 17. February 2008, 21:53:38
Today I was wondering about these modern CSS properties that call themselves "standards". There's all this fancy stuff, text-overflow, inline-block, ellipsis and so on. But then; there's a ton of browsers, not just IE, Safari, Opera and Firefox. There's Konqueror, Epiphany, hv3 (a browser based on tkhtml), etc... And if there's a site which uses these, at least one of these browsers won't display it correctly. I'm taking that as "enough to ruin a standard".
I recently made a small site for my freetime project t2i and I only needed font (for defining size, family and weight), color and background-color. Yet it displays quite good for me in ALL browsers I can get my hands on.
My CSS happens to be this small:
My point is: why do people nowadays need such properties that claim to be standards but in a way aren't? Why don't sites just use these "basic building blocks" instead of using elements that ruin the sites in minor browsers?
Comments welcome
I recently made a small site for my freetime project t2i and I only needed font (for defining size, family and weight), color and background-color. Yet it displays quite good for me in ALL browsers I can get my hands on.
My CSS happens to be this small:
body {
font-family: sans-serif;
background-color: #111;
color: #EEE;
}
#leftbar {
width: 155px;
}
#head {
font-style: italic;
}
a, a:visited { color: #08F; }
a:hover { color: white; }
My point is: why do people nowadays need such properties that claim to be standards but in a way aren't? Why don't sites just use these "basic building blocks" instead of using elements that ruin the sites in minor browsers?
Comments welcome








Ulrich Holtzhausen # 25. April 2008, 14:10
Personally, I have no problem with the fancy stuff as long as they work in all browsers, obviously text-based browsers are excluded, but a site should yet be usable in one of those.
If something is a standard however the browsers should make the effort to comply with it, not the other way round. The latest public build of WebKit passes the Acid 3 test, Opera 9.50 will pass the Acid 3 test (and the developer build already does) and Firefox 3 is also expected to pass the Acid 3 test.
IE has never complied with standards as they are a bunch of ignorant bastards who think they can enforce any new rules into web design.
That said, if Opera, Firefox, Safari (and Konqueror) can pass the Acid 3 test other browsers should be doing the same.