Comments on: What CSS 3 Can You Easily Use Right Now?

By: Jarett

Jarett — Tue, 02 Nov 2010 01:54:36 +0000

CSS3 will be available in IE9, which is available in Beta right now, so we could be there soon! I don’t want to, as many of you don’t, build another site with outdated tech, so as soon as M$ gets this out, the better for all of us FF, et al, users. It would be foolish, however, to think the user will perform updates to their PCs or even Macs as suggested, so I guess backward compatibility will still be necessary for a long time.

By: Dan

Dan — Fri, 09 Jul 2010 06:30:39 +0000

I just Googled “safe to use css3 now” and it took me several seconds to work out that result #1 (this post) was from 2007, and therefore no longer accurate..

By: Aden Fraser

Aden Fraser — Wed, 27 May 2009 16:28:23 +0000

Firefox 3.5 Beta 4 works with Border Images and various others ;)

By: WEB 3.0 » Blog Archive » �As� que quer�as saber (casi todo) de CSS?

WEB 3.0 » Blog Archive » �As� que quer�as saber (casi todo) de CSS? — Sat, 18 Apr 2009 01:34:15 +0000

[...] What CSS 3 Can You Easily Use Right Now? – Peter Gasston [...]

By: David Storey

David Storey — Thu, 26 Jul 2007 14:50:15 +0000

juFo: Not as easy as you may think. I assure you. I’d assume CSS2.1 is a priority for the IE team at present, and that is only right as that is what is in most use today.

By: marC

marC — Thu, 26 Jul 2007 14:24:44 +0000

Well why don’t we add some pressure over here:
http://blogs.msdn.com/ie/contact.aspx

http://blogs.msdn.com/ie/ (the IE blog)

By: juFo

juFo — Thu, 26 Jul 2007 02:11:45 +0000

how hard can it be for microsoft to add everything working in IE…
If they find a bug in windows wh000 then in 5 seconds you see a reaction and the next day there is a patch for it.

It’s not fun making websites and then trying to fix you code with hacks for IE (that most of the time don’t work)

What we need is CSS3 (now and not in another 5 years), Internet Explorer 8, Firefox 3, etc
who ALL use the same standard!

Come on make some pressure!

By: David Storey

David Storey — Tue, 24 Jul 2007 22:12:44 +0000

I don’t think we need a new spec like CSS2.2, just for browsers to agree on which features are the priority to implement and for all browsers to implement the same features as their schedule allows (instead of the current situation where Opera implemented Media Queries, Mozilla implemented border-radius, Safari did text-shadow etc). To do this we need to know from developers what the most important features are. I’ve had some feedback on this. We also need those parts of the specs to be firmed up so there won’t be a case where each browser implements it differently as the spec wasn’t mature enough. You could give it a name like CSS3.1 or CSS3 basic profile or such, or just create an interim module with all the properties that are ready to be implemented and are desired by developers.

There doesn’t really have to be anything formal from the W3C except the commitment to work on the few things that are desired but the spec isn’t quite ready for implementation sans the browser prepends.

By: fantasai

fantasai — Tue, 24 Jul 2007 20:09:21 +0000

Creating CSS2.2 would be a ridiculous amount of unnecessary work. What would be far less work but be just as effective would be CSS2.1 + some key CSS3 modules that spec the features you want. I’d rather see a campaign formed around communicating what those features are to the working group and pressuring them and the implementors to work on those features.

By: GreLI

GreLI — Tue, 24 Jul 2007 11:19:32 +0000

With conditional comments and other IE tweaks you can use cool effects in modern browsers. E.g. “box-sizing: border-box” (and -moz-box-sizing for Firefox) is very usefull for setting form elements dimensions. Also you can use opacity in most modern browsers and set filter for IE and so on…
However there are things that can be done in IE without scripting. But why not use them for modern browsers users encouraging them in doing this?