The time is now 10:22 pm You last visited November 22, 2009, 7:00 pm | Comments for "Supporting Google Chrome with Browserhawk"September 3, 2008, 6:37 pmSupporting Google Chrome with BrowserhawkLottery 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:
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. In addition to seeing that it is correctly identified, also be sure cookies and JavaScript are being detected as "enabled". CommentsYou must be a Lottery Post member to post comments to a Blog. Register for a FREE membership, or if you're already a member please Log In. |
WOW, what a coincinink...