Transform Origin is forced to 0,0 when using 'Responsive Scaling' in mobile Safari and Chrome

I have found this exact issue today as well today.
I created these character animations a couple of weeks ago and they were fine:

http://www.theboxtrolls.co.uk/

but today I have noticed that many of the rollover transform origins have reset to 0,0

...see sparky character hanging from roof, lights hanging from roof, and fish character's arm on the right hand side of the video panel

in the Edge Animate source file, the origins are fine and scrubbing the time line the animation is correct, but in the published file, the animation origins are incorrect

I have remade one of the animations and re-published it, which seems to have fixed the issue, but I don't want to have to remake all of these animations!!!!!!

Please advise what we can do to address this issue

I have a similar issue with Chrome browsers since they updated to version 36. Previously in version 35 all of our character animations worked great. Now, since the update to 36 their arms, heads and other child symbols that had a scaled origin point is off position. This makes their heads and arms come flying off in animations, and that really scares the kids! (Children's education software.)

Need to know an issue on this quickly as well. We've got product deployed that was good until Friday and this is as far back as the issue can be traced. Help!

Thanks,

Dave

I'm in the very same situation than Dave, also with childrens education software. Every item in my animations have changed the origin to 50,50.

I've test with a unactualized chrome to see an animation and it displays ok, after the actualization, every item change the origin and displays wrong!

Hope this image helps to clarify this issue to developers a bit. It seems that any child symbol inside of a parent fails to have it's transform-origin set correctly now in Chrome. Only a default value of 50%, 50%, 0px is passed along.

Let me know if you all have any suggestions or other ways to solve this. Bit of a nightmare way to start off a Monday, last years worth of work is breaking all over the place as customers update their browsers.

Slight update - with a caveat that I am not a developer!

"inspecting element" in chrome I noticed that the webkit-transform-origin property of the offending elements had been overridden by a transform-origin property (see screenshot below)

this new transform-origin is set to 50%, 50% rather than the values of the webkit-transform-origin (86%, 9%).

looking at exactly the same page in firefox, the coordinates for transform-origin are correct and hence works correctly

looking at caniuse for transforms - http://caniuse.com/#search=transf

It appears that Chrome has moved from transforms with prefix -webkit to straight transform with the latest update to version 36.

I think that there is a bug in the code that generates the css on the fly depending on the browser that is viewing the page.

For some reason, if the browser is chrome, 2 versions of the css need to be generated (with and without -webkit for chrome versions before and after version 36), unfortunately for version 36, the code is generating the default values of 50%, 50% rather than the whatever the origin was set to!

fix is needed ASAP please Adobe!

great minds think alike :-)

Condensed these thoughts into a single new post that will hopefully draw some attention for a fix. Link below.

BUG: transform-origin not properly being set for Chrome v36

Hi All ,

We have addressed the vendor prefix problem on Chrome v36. The new Edge Animate CC 2014 updater(2014.0.1) is now available on Creative Cloud. Please install the build and do let us know if your animations are now working as expected on Chrome.

Please refer to the What's new @Edge Animate Help | New features summary for more details.

Thanks and Regards,

Sudeshna Sarkar

Hi,

I have updated to Edge Animate 2014.0.1

The problem is still in Mobile Chrome 36 when project setting Override is "visible". it does not do Responsive Scaling. (see .png images)

If project setting Override is changed to "hidden". It works