It would be easy to carve out older versions. However the penetration
numbers show that basically 99.99% are on 9+. So I didn't bother.
IMHO anytime software can help prevent user confusion, it should.
Alan
On Feb 21, 12:35 am, Philip Hutchison platelu...@gmail.com wrote:
Hi Alan
I applaud
Hi Alan
I applaud your efforts and understand your arguments. However, your code
fix is aimed at preventing any Flash Player instance below 10.0.42 from
invoking ExpressInstall. Earlier versions of Flash Player were certainly
capable of running ExpressInstall (it has been around for years), and
While I agree that this isn't SWFObject's fault, that doesn't mean
swfobject can't do anything about it.
I just patched the source on the swfobject.js that we use to fail over
to the alternative content if the person is on a setup that won't
properly expressInstall. Our alternative content
Bottom line is: Flash Player's Express Install functionality is not
completely reliable, and there's really not much SWFObject can do about it.
The Express Install experience -- when it works -- varies from browser to
browser. Express Install is a great idea, but has always suffered from a
So the only things which swfobject can control in regards to the process
(after determining an update is required) is:
loaderClip.redirectURL = _level0.MMredirectURL;
loaderClip.MMplayerType = _level0.MMplayerType;
I just tested ExpressInstall on a bunch of Flash versions running in
IE and FF on Win XP SP2, and here are the results:
WIN Flash Player 10,1,82,76
WIN Flash Player 10,1,53,64
WIN Flash Player 10,0,45,2
WIN Flash Player 10,0,42,34
FAIL Flash Player 10,0,32,18
DID NOT TEST Flash Player 10,0,22,87
The bug actually happens in all browsers. I am not sure it's actually
happening after you hand over control to Adobe. I think there's a bug
in what happens after the download is complete...
I just recorded a screencast of the situation here:
So the only things which swfobject can control in regards to the process
(after determining an update is required) is:
loaderClip.redirectURL = _level0.MMredirectURL;
loaderClip.MMplayerType = _level0.MMplayerType; (inside