I have tried to publish my Flash files as 11, 11.2, 10.3 etc., and they all read as Flash Version 12 in the DoubleClick Flash Validator. When I change to output version 8 it reads as version 8.
When you "Publish" a Flash .fla file, Flash creates some HTML code and places the compiled .swf on a Web page. In the Publish settings there are some options as to which version of Flash (Browser Plugin) you want to target. You can even target versions that don't work with your particular .swf!
From that point on, any "validation" has to do with the HTML code and has nothing to do with any actionscript 1, 2, or 3.
The "Publish Settings" as well as the "Published" HTML code is mearly a suggestion. It is neather neccesary nor often "the best way" to place a compliled .swf on a Web page.... it's only a suggestion.
So if the "suggested" HTML code doesn't suit you, change it! you can hand code the .swf to whatever version will play your .swf.
My advice, target the LOWEST version of Flash that will correctly display the .swf, never the highest.
And if you HTML code is correctly targeting version 10 of the Flash browser plugin, and the Double Click Flash Validator says you are validated at version 12.... ignore them. They are wrong!
The HTML code will tell the true story.
You can validate your own Flash by simply looking at the HTML code on the Web page (or post a link here and we can tell you). It ain't rocket science!
Although I really appreciate the response, and the info within, I can't ignore the validator because the people at DART are demanding that the banner files read as Flash Version 10 or under. I think this 'bug' is a big problem!!!
Then post a link to the actual Web page and the "Adobe Flash Pro" Forum will validate the ACTUAL Flash version coded into the HTML, not some knock-off wanna-be.
And again, the bug is NOT an Adobe problem, it's a Double Click Flash Validator problem.
You can easily resolve this with just a link to the Web page!
This problem was created by Adobe. I created a custom preview utility for the Flash files we create where I work and in doing that I added code to detect what version the Flash file is published to using FlashTools.dll in a .Net app and it's reporting mostly the same thing:
10.3 = 12
11.1 = 14
11.2 = 15
What it is doing is reading the first few bytes of the .swf file, which I believe Double Click Flash Validator is probably doing the same thing, maybe with the same .dll. It's not a Double Click Flash Validator problem, it's how Adobe decided to change the version encoded in the .swf file.
From an Adobe blog post (http://blogs.adobe.com/rgalvan/2011/11/adding-fp11-support-to-flash-pr o-cs5-and-cs5-5.html), the versions are out of sync. I think this is because they started adding bigger features to the published .swf but needed only smaller Flash Player updates.
Flash Player 9 = swf version 9
Flash Player 10 and 10.1 = swf version 10
Flash Player 10.2 = swf version 11
Flash Player 10.3 = swf version 12
Flash Player 11 = swf version 13
Europe, Middle East and Africa