Lottery Post uses Browserhawk (from Cyscape) to detect browser capabilities, so if a user's web browser does not meet the minimum standards required by the site, they can be shown a detailed message page, with a description of exactly what is under-functional.
When the new Google Chrome Web browser was released in the past week, Browserhawk did not detect the new browser properly (and still does not), so users of the new browser had problems logging in to the site.
Since Chrome uses the Apple WebKit open source codebase as its foundation, Browserhawk mistakenly detected the browser as Safari 1.0.
To remedy the situation — at least until Cyscape updates their browser definitions — I have re-programmed the main browser definition file to detect the Chrome browser as Safari 3.1. (Under the covers the Chrome rendering engine is Safari 3.1.)
For anyone else who uses Browserhawk for browser detection, adding Chrome to the browser definitions is fairly straight-forward:
- Open the Browserhawk Editor.
- Select File, Open..., and then select maindefs.bdf and click Open.
- Right-click on the Safari folder (in the left folder/browser list), and click Add... in the context menu.
- In Browser Description enter Chrome.
- In Identifying user agent string enter Mozilla/*AppleWebKit/[5-9][0-9][0-9]*Chrome*Safari*.
- Click OK.
- Change Majorver to 3.
- Change Minorver to 1.
- Change Version to 3.1.
- Change Fullversion to 3.1.
- Make sure the rest of the properties match the properties in the Safari v3 entry by clicking back and forth between Chome and Safari v3 — except for the last two properties.
- Set Versionposx to 0 [zero].
- Set Versionposstr to an empty string.
- Click the Save icon in the editor toolbar to finish the process.
To test to be sure Chrome is being properly identified as Safari 3.1, go to www.mybrowserinfo.com and click on See Detailed Location and Browser Information.