Apple Releases Safari Technology Preview 29 With Bug Fixes and Feature Improvements

safaripreviewicon Apple today released a new update for Safari Technology Preview, the experimental browser Apple first introduced one year ago in March of 2016. Apple designed the Safari Technology Preview to test features that may be introduced into future release versions of Safari.

Safari Technology Preview release 29 includes fixes and improvements for JavaScript, CSS, Rendering, Web Inspector, WebCrypto, Accessibility, Media, and more.

The Safari Technology Preview update is available through the Software Update mechanism in the Mac App Store to anyone who has downloaded the browser. Full release notes for the update are available on the Safari Technology Preview website.

Apple's aim with Safari Technology Preview is to gather feedback from developers and users on its browser development process. Safari Technology Preview can run side-by-side with the existing Safari browser and while designed for developers, it does not require a developer account to download.

Tag: Safari Technology Preview

Top Rated Comments

MLinneer

116 months ago

Safari Tech Preview stomps the completion on the Basemark 3.0 Browser Stress test on my 13" MacBook Air:
STP 29 - 597.29
Safari 10.1 - 324.26
Chrome 57 - 294.20
Firefox 53 - 176.78

Score: 5 Votes (Like | Disagree)

CPx

116 months ago

Wow, they finally fixed adding bookmarks to the bookmarks folder! Only took 1000 years!

Score: 3 Votes (Like | Disagree)

Mac-lover3

116 months ago

When is Safari for Windows getting an update?

Isn't Safari for Windows already dead some time ?

EDIT: it is already dead since 2012.

Score: 3 Votes (Like | Disagree)

MrNomNoms

116 months ago

The Firefox team lost their way a long time ago.

IMHO everything turned to crap the moment they decided that writing the UI in XUL was a good idea - if they created the UI in the native UI kit (Cocoa for Mac, Win32 (the later on XAML) for Windows, GTK+ for *NIX) then it would have avoided the mess that added bloat to the core of the project (which is why Apple adopted KHTML/KJS instead of Gecko) and if they went with the extension framework being used by Webkit earlier on then a lot of the problems could have been avoided.

Score: 1 Votes (Like | Disagree)