Comments on: CSS Transforms: First WebKit, now Gecko too!

By: pmontrasio

pmontrasio — Tue, 16 Sep 2008 07:31:59 +0000

@Salva: I understand the reason for prefixes, but it’s a pain and I don’t understand this double standard between draft html tags and draft css declarations.

This draft thing is a nonsense because different browsers keep behaving differently even on standardized things like paddings, borders, margins and tables. I really don’t see many differences between draft standards and having to deal with IE6/7, FF2/3, Opera, Safari and now Chrome.

A solution would be implement both the browser specific declaration and the standard one (i.e. both -moz-transform and transform): developers that want to play safe will use the former, developers who want to take risks will use the latter. Furthermore, there aren’t more risks in the latter approach than in dealing with the usual incompatibilities between browsers: test a lot, fix the layout and the css, iterate.

By: 115516

115516 — Mon, 15 Sep 2008 19:26:06 +0000

This is very good!
CSS3 – to the all browsers!

By: Salva

Salva — Mon, 15 Sep 2008 16:07:59 +0000

The prefixes are there to avoid compatibility problems if the finished spec is different from the current implementation. They are a pain, but having suffered the effects of “padding” not working equally across browsers, I guess it’s not that bad.

I can’t wait for the prefix to dissapear, thought, as it will mean a standard has been reached and the properties can be used safely.

By: westonruter

westonruter — Mon, 15 Sep 2008 16:06:05 +0000

Hope Mozilla unveils CSS Transitions at the same time as Transforms.

IE’s matrix filters are a pain to use. Try, for example, applying a rotation transform to an alpha-transparent PNG. IE’s filters aren’t integrated deeply enough into the rendering engine.

By: pmontrasio

pmontrasio — Mon, 15 Sep 2008 15:20:36 +0000

Nice, I’ll experiment with them to learn the tricks but I think I’m not using them in my projects until browser vendors remove the -moz/-webkit prefixes from the declarations. I don’t want to use both -moz-transform and -webkit-transform in my CSS files, maybe with even different arguments and results.

Gecko 1.9 alpha is using the video tag and not a moz-video one, even if HTML 5 is still a draft recommendation. Why can’t they do the same for CSS transforms, which are in draft stage as well?

The same happened with border-radius weeks ago.

By: sergeyilinsky

sergeyilinsky — Mon, 15 Sep 2008 15:11:42 +0000

Lon42, very good reminder on IE’s (oh, that old new kind-of-browser) original “missing” implementation…
BTW: It’s getting really fun with all “standardization” efforts. Imagine CSS files full of:
-moz-transform: translate(30px);
-ms-transform: translate(30px);
-webkit-transform: translate(30px);
-safari-transform: translate(30px);
Wish we had more browsers willing to participate the rush ;)

By: Lon42

Lon42 — Mon, 15 Sep 2008 14:57:01 +0000

The title should be: First IE, then nobody, then WebKit, then Gecko as IE offered Matrix transformations in IE5.5, released july 2000.

That doesn’t mean I’m not happy with current developments.

But. Where’s the z-axis in Gecko? No 3D rotations/translations yet?