Type: Integer
This property returns 0 if the user has Flash installed and working, 1 if the user has Flash installed but it is blocked or otherwise not working, and -1 if the user does not have Flash 10 or higher installed.
Special Installation Step
Before using this property you must place the bhawkcap.swf into the same web directory where your scripts resides that performs the Plugin_FlashBlocked property check. This step is not performed for you automatically during installation of BrowserHawk. Therefore you must do so manually. For example, if your web page that tests Plugin_FlashBlocked is \inetpub\wwwroot\mysite\bhtest.aspx, then the swf must be placed in that same directory where the bhtest.aspx file resides. BrowserHawk for ActiveX and .NET users can find the bhawkcap.swf file in the \Program Files\cyScape\BrowserHawk folder. BH4J users can find this file in the BH4J zip distribution. This file is needed because BrowserHawk uses this Flash file to test whether the browser can load and execute it. Note that the Flash it executes for this test is completely transparent.
Note: This property requires either the Professional or Enterprise Edition of BrowserHawk.
C# Example:
<%
ExtendedOptions options = new ExtendedOptions();
options.AddProperties("Plugin_FlashBlocked");
ExtendedBrowserObj extBrow = BrowserObj.GetExtendedBrowser(options);
%>
<html>
Plugin_FlashBlocked: <% Response.Write(extBrow.Plugin_FlashBlocked); %> <br>
0 = Flash is working and not blocked, 1 = Flash is blocked, -1 = no Flash 10 or higher installed
</html>
Special notes for this property:
Returns 0 if Flash is installed and working, 1 if Flash is blocked, -1 if Flash 10 or higher is not installed, -2 if JavaScript is disabled, or another negative value if an unexpected error occurs during testing.
Not all Flash blockers or other such reasons for Flash being blocked are detectable. In these cases this property may return 0 yet the Flash may still be blocked.
If you are consistently receiving a returned value of 1 for this property for all users (indicating Flash is blocked) when you are certain that Flash is indeed not blocked, then it means the bhawkcap.swf file needed for this test is not in the right location. See the Special Installation Step note above.
When testing users on OS X, in some cases it may take their machine several seconds to initialize Flash and begin executing this Flash based test. In that case, BrowserHawk may return that Flash is blocked when it is not, because the test times out. By default BrowserHawk automatically increases its time out threshold for this test for users on OS X. However if you find that even more time is needed you can instruct BrowserHawk to allow more time for this test to complete by setting the FlashTimeout option prior to executing the extended property test.
If the user’s JavaScript is disabled this property will not be available.
See Also: