Comments on: Why and when browsers prefix CSS3 features

By: Browser specific prefix « Eureka Design

Browser specific prefix « Eureka Design — Wed, 06 Jan 2010 22:39:01 +0000

[...] css3.info [...]

By: EGB

EGB — Wed, 10 Sep 2008 14:11:12 +0000

I still didn’t find a real time working example of css3 from a to z :(

By: Joost de Valk

Joost de Valk — Tue, 04 Jul 2006 07:38:14 +0000

Karl: thx! i’ll update the page, any other comments? :)

By: karl

karl — Tue, 04 Jul 2006 01:06:31 +0000

Multi-column doesn’t work only in Firefox, but all Mozilla family including Camino

By: Joost de Valk

Joost de Valk — Fri, 16 Jun 2006 22:19:41 +0000

The funny thing is, moz invented border-radius, and the W3C added it later. Moz prefixed it, because if they didn’t the W3C couldn’t decide how the pref should work: it would have to work exactly like mozilla, or it would break existing content.

(Thanks to Ian Hickson btw, for helping me on this small post :) )

By: Peter Gasston

Peter Gasston — Fri, 16 Jun 2006 21:51:27 +0000

Unless I’m mistaken, the -moz-border-radius (and perhaps -webkit-border-radius) declarations do not match the border-radius CSS3 declaration; in -moz-border-radius you choose only one value, whereas the border-radius draft allows you to choose two values to have more flexibility in the curve.

For example;

-moz-border-radius: 1em;
border-radius: 1em 2em;

A good example of why some declarations are not fully implemented yet.