Comments on: CSS3 breaking in the design community

By: Joeri

Joeri — Tue, 16 Jun 2009 11:13:34 +0000

As long as a particular CSS3 module isn’t finalized, vendor prefixes are used in case there are last minute changes. This allows the standards process to get implementation feedback while not having to actually take implementations into account. The box-shadow property is from the “backgrounds and borders” module which is still in draft status.

By: rasmusfl0e

rasmusfl0e — Tue, 16 Jun 2009 09:42:37 +0000

@AMIGrAve: I was bemoaning the fact that no browser (that I’m aware of) supports CSS3 without the use of vendor prefixes – I would much rather have them to omit prefixes altogether. I just wish the transition to prefix-free CSS3 support was faster.

By: AMIGrAve

AMIGrAve — Tue, 16 Jun 2009 09:23:46 +0000

> Especially considering the different vendor prefixes that are still needed. *ugh*

Please, help me understand why vendor prefixes are needed if the correct css3 implementation is done ?

Why should we use :
-moz-box-shadow: black 10px 5px 5px;
-webkit-box-shadow: black 10px 5px 5px;

instead of:
box-shadow: black 10px 5px 5px;

I guess there’s a reason !? Is it a transitional state ?

By: Schill

Schill — Mon, 15 Jun 2009 22:58:40 +0000

For what it’s worth, it looks like -moz-box-shadow is supported in the pending Firefox 3.5 release (as well as Safari 4.) I look forward to not having to make any drop-shadow PNGs (or GIFs, even.)

By: rasmusfl0e

rasmusfl0e — Mon, 15 Jun 2009 20:31:14 +0000

By the looks of it there won’t enough wide spread support for CSS3 (or HTML5) in browsers (given IE’s prime cut) anytime soon… Especially considering the different vendor prefixes that are still needed. *ugh*

That AmpleSDK makes more sense minute by minute.

By: CaptainN

CaptainN — Mon, 15 Jun 2009 18:31:26 +0000

Any CSS3/HTML5 to CSS2.1/HTML4 compilers? There seem to be enough standard hacks out there to pull something like that off these days. :-)

By: davidlantner

davidlantner — Mon, 15 Jun 2009 17:23:32 +0000

Remy Sharp analyzed Tim's design in a screencast at jQuery for Designers that includes a jQuery-based alternative for the (WebKit-only) CSS Transitions.