We'd like to move away from the dedicated <transform> element and focus on using CSS transforms instead. However since these need to be packed into the style attribute along with the new visibility properties, we need to offer some kind of library or toolset so the user doesn't have to parse strings when wanting to change a transformation.
The tools should allow setting, changing or removing any transformation property (eg. translate3d, rotate3d, scale3d) without losing other transformation properties or CSS visibility information.
For simplicity we may limit the system to a single property per transformation type (eg. you cannot have two rotate3d() properties on the same element).
We'd like to move away from the dedicated
<transform>element and focus on using CSS transforms instead. However since these need to be packed into thestyleattribute along with the new visibility properties, we need to offer some kind of library or toolset so the user doesn't have to parse strings when wanting to change a transformation.The tools should allow setting, changing or removing any transformation property (eg.
translate3d,rotate3d,scale3d) without losing other transformation properties or CSS visibility information.For simplicity we may limit the system to a single property per transformation type (eg. you cannot have two
rotate3d()properties on the same element).