Soon after the release of Plainview, we starting hearing about issues viewing pages that employ browser sniffing to look for compatible browsers, sites like abc.com where Safari is allowed, but Plainview is blocked. There was even suspicion that we were using an custom user-agent string which was causing trouble. Well, we weren’t, but we are now. Turns out that the sites mentioned, and many others it seems, are looking for “Safari” in the user-agent string, and WebKit does not identify itself as Safari out-of-the-box so these sites would believe Plainview to be incompatible. This is bad mojo. Apple recommends looking for “AppleWebKit” not “Safari” to ensure compatibility with WebKit powered browsers, and even offers some code to help out.

However, I hardly expect abc.com and their ilk to switch detect scripts overnight. So the next build of Plainview will include a tweaked user-agent string to identify itself as “Plainview (like Safari)” which seems to fix the issues with abc.com and hopefully others as well.