View Single Post
If it is in a later WebKit build then you'll need to wait for 5.5.1 before this is fixed, which OmniGroup is going to be starting on once 5.5 is final. 5.5.1 is going to be an update to a newer version of WebKit than the one they have currently picked so that these types of bugs will be solved, but they don't won't to delay the release of 5.5 further by starting on later WebKits right now.