Comment 10 for bug 132154
Revision history for this message
| Jens Vagelpohl (dataflake-deactivatedaccount-deactivatedaccount) wrote | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
FYI: OmniWeb 5.6 was just released, which appears to fix the issue all by itself, since I am actually able to view and comment on this bug report using OW. They updated the version of WebKit:
OmniWeb 5.6's user-agent string is:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/522+ (KHTML, like Gecko, Safari/522) OmniWeb/v613
OmniWeb 5.5's user-agent string is:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/420+ (KHTML, like Gecko, Safari/420) OmniWeb/v607
IMHO if you believe your fix is questionable or you are not 100% sure if it affects other browsers negatively it would be fine to pull it completely.