Safari Technology Preview 117 ships support for the individual transform properties defined in the CSS Transforms Module Level 2 specification. The spec takes the translate(), rotate() and scale() functions that were previously only expressible inside transform and promotes each to a property of its own: translate, scale and rotate.
Chained functions versus separate declarations
The conventional approach stacks all three functions on a single transform declaration:
.some-element {
transform: translate(50px 50px) rotate(15deg) scale(1.2);
}
With the new properties the same result can be written as three separate declarations:
.some-element {
translate: 50px 50px;
rotate: 15deg;
scale: 1.2;
}
Why split a shorthand into longhands?
CSS usually moves in the opposite direction, bundling longhands under shorthands such as background, border, font, margin, padding and place-items. The WebKit team gives several reasons for going the other way here:
- When only a single function is needed, one property is easier to write —
scale: 2;rather thantransform: scale(2);. - Chained functions carry a much higher risk of one transform accidentally overriding another; separate properties remove that hazard.
- Animating an individual property is considerably simpler than pre-computing and recomputing intermediate values for a chained
transform. - Timing and keyframes can be controlled at a finer grain, per property.
Order of application
The individual properties are not equivalent to an arbitrary reordering of the chained functions. They are applied first, in a fixed sequence — translate, then rotate, then scale — and only after that do the functions declared in the transform property take effect.
Support and feature detection
Coverage is very thin at the time of writing: essentially Safari Technology Preview 117 plus Firefox 72 and later, for roughly 3.9% global support across the three properties (translate, rotate, scale). The WebKit post recommends guarding usage with @supports:
@supports (translate: 0) {
/* Individual transform properties are supported */
div {
translate: 100px 100px;
}
}
@supports not (translate: 0) {
/* Individual transform properties are NOT supported */
div {
transform: translate(100px, 100px);
}
}
Rearranging the check to drop the not operator is an option, leaning on progressive enhancement instead:
div {
transform: translate(100px, 100px);
}
@supports (translate: 0) {
/* Individual transform properties are supported */
div {
transform: none;
translate: 100px 100px;
}
}
Either form clears the shorthand functions and lets the individual properties apply only in browsers that support them.



