[Webkit-unassigned] [Bug 70025] Merge CSS and SVG 2D Transforms according to FX 2D Transforms

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Oct 14 04:27:39 PDT 2011


--- Comment #7 from Dirk Schulze <krit at webkit.org>  2011-10-14 04:27:39 PST ---
(In reply to comment #6)
> (In reply to comment #5)
> > I'd handle it like in HTML when HW acceleration is disabled. Means Ignore z-value in origin and transform 3dtransforms to 2dtransforms. Origin attribute will be supported in SVG 2.0.
> I'm not very keen on this. I'd prefer to just ignore the property value, because it allows people to author their CSS in a manner that supports a fallback. In the future we'll support 3d in SVG, but for now people could write:
> transform: scale(2) rotate(10deg);
> transform: scale(2) rotateY(10deg);
> This way they still get to control the effect when 3d is not available. Also, flattened 3d transforms look horrible :)
Sure, but it would help in the meantime. I don't think that you want to deny 3D code in -webkit-transform
for SVG if we will support it later anyway.

> > 
> > Just another note: The origin default value differs between HTML and SVG. For SVG it needs to be (0%,0%) to the bounding box.
> Do we have to worry about that yet? Only when SVG supports the transform-origin property - then we'll need code to test whether it is in SVG or CSS.

I'm not sure. But I think I can remember that it was a problem. IIRC you had to pass the you bounding box at some point and that is used to calculate the origin for the transform. I definitely didn't thought about implementing transform-origin property at this time. Sadly I don't find my patch where I enabled CSS transforms in parallel to SVGTransforms. I'll search it later again.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list