View Single Post
Changing site prefs to identify as Safari 3.12 fixes this.