Wednesday, November 28th, 2007

Safari CSS Reference

Category: CSS, Tip, WebKit

<>p>Do you want to have one place that tells you about all of the Safari properties?

Now we have it.

The reference shows not only the standard properties and how Safari handles them, but also all of the -webkit-* properties such as -webkit-border-top-right-radius:

WebKit Border Property

Related Content:

9 Comments »

Comments feed TrackBack URI

And what about the “-khtml-” prefix?
Doesn’t it work with Safari?

Comment by Vinch — November 28, 2007

@site smart: They are using a browser-specific tags because the CSS3 style rounded border rule is classified as ‘experimental’. Once it moves to ‘stable’ the browser specific tag will be dropped.
.
See: http://developer.apple.com/documentation/AppleApplications/Reference/SafariCSSRef/Articles/ExplanationofTerms.html#//apple_ref/doc/uid/TP40006578-DontLinkElementID_5

Comment by Will Peavy — November 28, 2007

Any idea if these work with the iPhone version of Safari?

Comment by Steven Mileham — November 28, 2007

Yes, these properties work on the iPhone.

FF2 has its own implementation of the rounded corners properties as well.

Comment by don hosek — November 28, 2007

Sigh… more proprietary standards. I mean, understandably, it’s for something that doesn’t yet exist in a stable standard, but still. :P

Comment by mdmadph — November 28, 2007

This is the W3C’s encouraged mechanism for things that don’t meet a CSS recommendation, so it’s a good thing. Otherwise, it would never be possible to experiment and implement anything new. Something can’t be standard if there’s no working implementation…

Comment by Dylan Schiemann — November 28, 2007

Yeah, and it beats someone implementing something in the regular namespace (those properties that don’t start with a dash) that then gets widely used and HAVE to be accepted by other browsers because people like some of the commenters on here complain about compatibility. This method of adding experimental properties gives everyone a chance to test features as part of a full release without conflicting with the standard (or future standard changes). Plus, since the specific syntax of the property name (leading dash) lets everyone know it’s experimental, there is less chance of people using them in production code.

Comment by AndyB — November 28, 2007

>>that don’t meet a CSS recommendation
Actually there is a W3C proposed “border-radius” property
http://www.w3.org/TR/2005/WD-css3-background-20050216/#the-border-radius
so why to use proprietary name for it?

Comment by Maxim Kozhukh — November 28, 2007

Actually there is a W3C proposed “border-radius” property
http://www.w3.org/TR/2005/WD-css3-background-20050216/#the-border-radius
so why to use proprietary name for it?

If the standard is not finished and still a draft document/work in progress, as it states at the top of the page you linked to, then it is better keep the proprietary name to avoid conflict with the finished standard if and when it comes out.

Comment by Jordan — November 28, 2007

Leave a comment

You must be logged in to post a comment.