Comments on: A quick note on border radius

By: Samuel Turner

Samuel Turner — Sun, 29 Aug 2010 17:08:41 +0000

Seems this is now sorted with Safari 5, must have updated to the new webkit engine. :)

By: Laz75

Laz75 — Wed, 28 Jul 2010 15:30:15 +0000

Just a short note to say that Safari 5 supports the shorthand rule. Or “rules” actually, for it supports the standard one too now, like Chrome.

By: Levi Freeman

Levi Freeman — Sat, 08 May 2010 02:01:58 +0000

Internet explorer 9 recognises border-radius, hopefully all browsers will begin to use this…Oh and its finally happening, IE will have css3! in terms of border radius, it kind of does it better than safari, firefox or chrome!

By: Agustín Amenabar

Agustín Amenabar — Thu, 18 Mar 2010 17:47:03 +0000

Indeed Plain Chrome 4.1.249.x honors border-radius, no need for -webkit-
let’s hope Safari updates accordingly in the short term.

By: Laz75

Laz75 — Wed, 10 Mar 2010 10:19:30 +0000

I also just noticed that (dev) Chrome apparently honors the simple “border-radius” (no “-webkit”)… that’s why it works with the short-hand declaration, probabily.

I didn’t know that.

By: Jacob Bijani

Jacob Bijani — Tue, 02 Mar 2010 16:59:57 +0000

My attempt was to make it generate the most concise CSS it could. My impression was actually that the shorthand syntax was rather useless unless you were only setting one value. Each corner can take two values, which allows you to make radii with different curves. I read around and it seemed the safest bet was to not use shorthand syntax, because some implementations of the spec could treat a shorthand with 4 values as just two values for two corners.

Anyway, obviously you can write some code that would be a little better than what the tool makes. Thats not the point. You still are left with 4 lines of code that no one can remember. And anyway, the most likely use cases by far are setting them all to the same value or setting some values and leaving others as zero.

By: Alberto Calvo

Alberto Calvo — Tue, 02 Mar 2010 11:21:24 +0000

Chrome uses a newer version of Webkit engine. I bet your latest problem is because of that.

I really hope Apple updates the engine of Safari soon, as the Webkit team added a lot of CSS goodies and Inspector functionality that are great. Still waiting, though…