The browser number with a non-numeric element, 'v' in this case, was the cause of main version number detection failure. In the script, uncomment that case block, and the script will return the KHTML/Safari id, with the right AppleWebKit version number.
No modification necessary.Ĭustom requires a simple change in the code: search for: Please let me know if you have any questions at all about this. If this script could gain better support for OmniWeb that would be fantastic. This has helped us gain a lot of compatibility on sites where browser sniffing would often look for "Safari" instead of the Apple-recommended string of "AppleWebKit" (see ). Mozilla/5.0 (Macintosh U PPC Mac OS X en-US) AppleWebKit/85 (KHTML, like Gecko) OmniWeb/v496Īs you can see, we added the string "Safari" in the OmniWeb 5.1 release. Mozilla/5.0 (Macintosh U PPC Mac OS X en-US) AppleWebKit/85 (KHTML, like Gecko) OmniWeb/v558.36 Mozilla/5.0 (Macintosh U PPC Mac OS X en-US) AppleWebKit/125.4 (KHTML, like Gecko, Safari) OmniWeb/v563.15 The following are user agent strings for most released versions of OmniWeb with WebKit:
This script (Full Featured Browser Detection PHP Script) makes some account for OmniWeb, but fails to get the correct version number and has a value of FALSE for DOM compatibility (when really our DOM is the same as Safari's).
#Omniweb mac os x panther for mac os x
I am the product manager for OmniWeb, a browser for Mac OS X based on the same WebCore and JavaScriptCore frameworks that Safari is based on (from KHTML and KJS).
0 kommentar(er)
