Open GoogleCodeExporter opened 9 years ago
That behavior is probably by design and here's why...
Activating the express install swf seems to be an alternative to (i.e. mutually
exclusive with) calling the callback function with success=false.
If you set the embedSWF method's "xiSwfUrlStr" parameter from
"expressInstall.swf" to null, effectively deactivating it, then the function
specified by the "callbackFn" parameter is called with success=false as
expected.
Therefore, as a workaround, you could set the xiSwfUrlStr parameter to null so
the callbackFn parameter is called, then handle the success=false condition to
display a custom error message and/or manually activate the express install
feature. You could also perform a version check in that callback to ensure the
cause of the failure was an insufficient version rather than some other reason.
Original comment by Triynk...@gmail.com
on 4 Sep 2012 at 10:30
Original issue reported on code.google.com by
stransky...@gmail.com
on 13 Jun 2012 at 1:52