Did someone call me?
Thanks for the detailed information in your post Dave. We began looking into this a few days ago and you're right, the fix needs to come from our end to ensure Chrome stops trying to sniff out the -webkit prefix for transform-origin as this was recently deprecated in Blink.
Be assured that as Preran mentioned, this is a top priority for us right now. We can't publicly commit to a date because we just discovered this issue around the same time you guys did with the release of Canary 36 and legitimately don't have a firm date other than "soon". There's lots of shifting sands which goes into releasing an update, which include the fix itself, getting release builds ready, staging to ensure you can actually download it and deployment (plus all the little stuff in between). This isn't an excuse, totally understand you need this fixed now, just giving some insight that updates aren't magic (believe me, my life would be a lot easier if they were).
Sorry for the frustration, I understand how irritating these issues can be especially with deliverables due. Joys of working with the web. We'll keep you posted once we have a target date in mind (which will be soon) or if we come up with a short-term solution before a fix is available.
Thanks,
Sarah