As a result of BrowserHawk’s true data types and other improvements over browscap.ini, there are some differences in the values of certain properties that have been upgraded to use the appropriate data type or reflect are truer value.
These differences are outlined here. If your scripts check the value for any of these properties, you will likely need to update your script to use the new property value.
Under browscap.ini, the Version property is a string. Under BrowserHawk, it is a "double" (a numeric value supporting decimals). If you are making direct comparisons using the "=" operator, you should not be effected. For example, ’r;if browobj.version = "4.01"’ will remain unaffected – although you should consider removing the quotes around the version number now that it is not a string value. Comparisons based on less than and greater than can now be done directly without the need to account for the headaches that comparisons with strings can cause.
This is probably the biggest difference you will encounter. This is because the minor version number is now implemented as a Double, and not as an Integer as with browscap.
This means that a browser with a version of 4.02 will now have its Minorver set to 0.02, not "2" as it would be with browscap. As a result, you will need to update any comparisons in your script dealing with the Minorver property appropriately.
For example, a script which reads:
if browObj.Minorver > 2 then
…
should be modified to read:
if browObj.Minorver > 0.02 then
…
Under browscap.ini, the AuthenticodeUpdate property is set to a letter, such as "a" or "b" to indicate the version of Authenticode which the browser supports. BrowserHawk instead reports the AuthenticodeUpdate as an integer to indicate the specific version of Authenticode which the browser supports.
When using BrowserHawk, the Authenticode property is set to 0 if the browser does not support Authenticode. Otherwise it is set to either 1 or 2 to indicate the version of Authenticode supported.
See Also: