Practical Uses of CSS3(viget.com)
viget.com
Practical Uses of CSS3
http://www.viget.com/inspire/practical-uses-of-css3
4 comments
Which WebKit browser are you using? Chrome 3 in Windows failed on one of his examples (see my other comment).
And yes, very lame that IE gets none of these. None!
And yes, very lame that IE gets none of these. None!
I use the Webkit Nightlies at http://webkit.org.
Chrome fails at a lot of Webkit standard stuff.
Chrome fails at a lot of Webkit standard stuff.
I thought WebKit's WebCore would be to blame for this and not Chrome. Is it because Chrome (v3) is using outdated versions of WebKit or I am I misunderstanding what WebCore does (very possible)?
WebKit (Chrome 3) fails on his second input border radius example where all the corners are defined with one attribute:
-webkit-border-radius: 3px 6px 8px 10px;
Safari doesn't render it for me, but the WebKit nightlies do (they're <i>phenomenal</i>. Usually more stable than Safari, and faster than anything else). I guess I'm the opposite of you, as Chrome does.
I'm on a Mac though. Odds are versions are different if you're on a Windows machine.
As to the "bug in WebKit", only if it's supported in that version of webkit. Restart Chrome, and if it's still there, hunt for an existing bug report, and check if it's supposed to be supported. If yes, it's a bug. If no, then wait until a Chrome update (no clue how often they'll update the WebKit part of it, though).
As to the "bug in WebKit", only if it's supported in that version of webkit. Restart Chrome, and if it's still there, hunt for an existing bug report, and check if it's supposed to be supported. If yes, it's a bug. If no, then wait until a Chrome update (no clue how often they'll update the WebKit part of it, though).
This is not a bug in webkit. Safari renders it just fine.
I'm wondering why most of the larger browser makers don't get together to agree on something. The W3C can clean it up later.
I just don't think it would be too hard for Moz/Webkit team/IE team to agree to support 'border-radius' and other things. Any smaller browsers would catch on soon enough anyway.
Well, getting the IE team to get it to work may be a challenge.
I just don't think it would be too hard for Moz/Webkit team/IE team to agree to support 'border-radius' and other things. Any smaller browsers would catch on soon enough anyway.
Well, getting the IE team to get it to work may be a challenge.
In addition to the comment by Bodhi, I feel I should point out that this is a HORRIBLE idea. Microsoft has been doing this for quite a while, and that's part of the reason web support (among other kinds of support) is so nasty.
If anything, the W3C exists to make sure the standards don't conflict with themselves. When amateur spec-designers start throwing around specifications, run for the hills. There's going to be enough hellfire, brimstone, and general fail to satisfy any armageddon cult, but they'll all disagree on how the fail is going to happen. Endless hours will be spent in chatrooms and forums debating which fail will win, and in the end everyone has to crawl into their radiation-, mutant-rat-, gelatinous-ooze-, cosmic-ray-, alien-proof-bunkers every 37 minutes just to survive the onslaught of potential fail.
If anything, the W3C exists to make sure the standards don't conflict with themselves. When amateur spec-designers start throwing around specifications, run for the hills. There's going to be enough hellfire, brimstone, and general fail to satisfy any armageddon cult, but they'll all disagree on how the fail is going to happen. Endless hours will be spent in chatrooms and forums debating which fail will win, and in the end everyone has to crawl into their radiation-, mutant-rat-, gelatinous-ooze-, cosmic-ray-, alien-proof-bunkers every 37 minutes just to survive the onslaught of potential fail.
The W3C CSS working group is the browser makers -- and others -- getting together to agree on something.
http://www.w3.org/Style/CSS/members.php3
http://www.w3.org/Style/CSS/members.php3
Great article! It's a damn shame it's going to be another decade before we can actually use any of these properties and expect them to work...
As a remember: All of these work great in Webkit. Some of these things don't work right in Firefox (the drop shadows are rendered very badly, for example). And none of them at all work in any type of common IE.