Member
2012-08-11, 05:48 AM
This is also happening for me (OmniWeb v5.11.1 on OS X 10.8). I think the problem may be to do with Google's browser sniffing code, since setting the user agent string to OmniWeb 5.1 or Safari 4.3 seems to fix the problem.