ohem

"scale" isn't a property in canvas.  You need to use scaleX and scaleY.

Those templates are outdated; Adobe has made some changes to publishing since then.  If you're using Animate CC 2017, older templates won't work.
 
The best thing to do going forward is to reset to the default template, export it, and add back in any custom code such as linking to TweenMax, clicktags, the adsize meta tag, etc.  Then re-import it and you're good to go.

HTML5 expandable banners are definitely possible; how the functionality should be implemented will totally depend on the ad serving company, as they all have very different APIs.
 
For DoubleClick, you can get a template/starter file here: https://www.richmediagallery.com/tools/starterfiles#tplGeneratorPath:expanding%2F300x250%2Fimage%2Fborder%3Dfalse%3BautoExpand%3Dfalse%2Fe%2F500x500%2Fimage%2FexpandingDirection%3Ddr~
 
For Sizmek, here: http://showcase.sizmek.com/formats/demo/html5-expandable-banner
 
Adform here: http://creative.adform.com/support/documentation/build-html5-banners/html5-banner-formats/single-file-expanding-ad/
http://creative.adform.com/support/documentation/build-html5-banners/html5-banner-formats/double-file-expanding-ad/
 
Etc.
 
The size of the expansion will usually depend on the media buy/specs for various sites.  Many sites have specific dimensions like a 300x250 should expand to 700x500 or something like that... but expanding to full screen is possible if it's allowed where your ad is running.
 
Sizmek has an example of a banner that expands to full screen already built out: http://showcase.sizmek.com/formats/demo/html5-full-screen-expandable-banner and Doubleclick has an article about expanding to full screen too: https://support.google.com/richmedia/answer/4526014?hl=en
 
Can't offer much more advice unless you know how your ad will be trafficked.

If I'm understanding correctly, you just want to change the transform origin, so that your animation contracts from left to right, without adding a float in your CSS.
 
I would do it like this: 
See the Pen PzKkqm by ohem (@ohem) on CodePen

It's smoother with a faster/shorter tween and a more intense blur: 
See the Pen oLXPwZ by anon (@anon) on CodePen

Check out my answer to the same question here: https://forums.adobe.com/thread/2147715
 
 
Edit:
 
In the case of the particular starter file you're using, the clicktag is targeting the whole stage with 
stage.on("stagemouseup", doClickthrough); so that when you click anywhere on the stage the clickthrough fires, no matter what other buttons might be there.  
 
Removing the above code, adding an invisible button underneath your replay button that fills the whole stage, and adding this code
this.myBtn.on("click", function(evt){ window.open(clickTag, "_blank"); }); should help, though for some reason when I test it with that particular starter file/template, I seem to have to delete  
stage.enableMouseOver(); for the clickthrough to continue working.
 
There's a lot going on in that template so I can't troubleshoot further right now, but I can tell you that the issue you were experiencing was due to the whole stage being targeted on click.

Just add a position, like this:  
See the Pen MyVwNv by anon (@anon) on CodePen
 
More info about the position parameter here: http://greensock.com/position-parameter

Since you just want it to darken, you could do that by putting a black div above the image and tweening the opacity (autoAlpha)... like this: 
See the Pen ONzaQj by ohem (@ohem) on CodePen
 
 
Edit: or to avoid an extra "overlay" div, you could also use pseudo elements and the CSS Rule plugin like this: 
See the Pen NNXeKL by ohem (@ohem) on CodePen
 
Edit2: Just realized I was over complicating things with that first edit; you can skip the pseudo element & just put the image in a div with a black background, and then animate the opacity of the image itself, like this: 
See the Pen WwdmNO by ohem (@ohem) on CodePen

If you update the Greensock CDN links to the 1.18.2 versions, that fixes it:
<script src="https://cdnjs.cloudflare.com/ajax/libs/gsap/1.18.2/TweenMax.min.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/gsap/1.18.2/plugins/TextPlugin.min.js"></script> The "latest" CDN links are often not actually up to date, so something about those versions was causing the issue.

Apparently it was actually not the external libraries but the file size of the backup image being added to the ad, even though it was uploaded outside of the workspace.
 
Still kind of frustrating that they're counting backup images now, but good news for GSAP at least.

You can't stagger with just TweenLite, but you can stagger with TimelineLite or TweenMax.
 
http://greensock.com/docs/#/HTML5/GSAP/TimelineLite/staggerTo/
http://greensock.com/docs/#/HTML5/GSAP/TweenMax/staggerTo/

I was looking at this last night and it was really bothering me; definitely a bug with Safari.  
 
The only thing I found that seems to work is this solution: http://stackoverflow.com/questions/5736503/how-to-make-css3-rounded-corners-hide-overflow-in-chrome-opera/10296258#10296258
 

See the Pen ZbwXeo by anon (@anon) on CodePen

y: "-=300" does the trick.

You can optimize the SVG itself using SVGO: https://jakearchibald.github.io/svgomg/
 
Here's my attempt at cleaning up the JavaScript a bit: 
See the Pen ojdPRp by ohem (@ohem) on CodePen

You need to include CSS Plugin in addition to TweenLite & Ease Pack.

That doesn't seem right.  SVG is vector, and for simple outlined type the file size should be pretty low.  Are you sure you're converting the text to outlines?
 
When I try saving a SVG from Illustrator of the Rockwell font with every letter of the alphabet, uppercase and lowercase, the file size is still only 21k.  If I optimize it using SVGO, it goes down to 17k.  Example attached!
 
PNGs are fine for type too, though it's sometimes nicer to have something scalable.  Also, if you use PNGs you should create them at double size so that they're not blurry on retina displays.
rockwell_svg_test.zip

Are you sure the path is correct to your JS files? I recreated everything and it seems to work fine. 
 
Example attached.
test_update.zip

I've come across the same issue... adding force3D:false should fix it.  
 
force3D:true can also fix it, but it makes the text appear thinner in Safari so I prefer false.
 
If you don't mind the text being slightly thinner you can also just do this in the CSS; that fixes it too: 
-webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale;