barklund

I completely agree. I don't know what the browser should do either The only reason I have a css transform property on my element is because of GSAP's draggable. I'm currently trying to re-create my setup, but it clearly seems I need to do more that what I have in this simple example. Now adding Snap.svg and other stuff. The error is most likely between all the libs, but the result is that Draggable works on the css property and TweenMax works on the dom attribute. I'll try to demo it That's because of the transform property in the css on the .circle class. That's exactly the behaviour I wanted to illustrate. Not in my particular setup

Hi Jonathan, In reality, my SVG child is a group (as is most often the case for any non-trivial SVG object). The codepen have been updated to reflect this: http://codepen.io/barklund/pen/bqreKO Group elements have no x (or cx) attribute and can only be moved/transformed with transforms (either CSS or DOM). In this case, what is the correct approach? And regarding Draggable, it's merely a consequence of the above. I can create an example if you like, but it's besides the point right here. I have made a workaround locally, but I still believe the above is a bug. Regards, Morten

I can see that Draggable internally use an applyObj to update the SVG position (which I assume is what sets the CSS property and not the DOM attribute), but even copying this internal variable out to the global scope (via debugging), setting applyObj.data.x and then invoking applyObj.setRatio(1) (exactly as Draggable appears to be doing internally in the render method) still only sets the DOM attribute. I can't for the love of everything sacred figure out how Draggable internally is able to set the CSS property. Nor what I should do to do the same thing. Help, please? Regards, Morten

Hi there, (newly registered, but long time user) I have a problem with SVG transitions. If I have a SVG object with a CSS transform and try to tween it, the tween will set an (ignored) DOM transform attribute and nothing happens. Using force3D has no effect, as it still only sets the DOM attribute and not the CSS property. Something is clearly wrong here. When is this an issue? When using Draggable, as Draggable sets the CSS property. Once a Draggable has been updating the value, I can no longer tween it - even if I kill the Draggable. Regards, Morten