Apple today released a new update for Safari Technology Preview, the experimental browser Apple first introduced more than two years 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 54 includes bug fixes and feature improvements for Clipboard API, Beacon API, Web API, WebRTC, and Web Inspector.
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.
Top Rated Comments
Basically not all points are equal. The missing input types are a problem. Not supporting WebM with Vorbis support isn't.
[doublepost=1524108358][/doublepost] set date = 2001 ; s/safari/firefox/g
I think you're probably implicitly referring to Google Chrome as being the browser for the "pro area," as it is the marketshare leader. I give you that Google is pushing for web standards, but I don't know that I agree that Chrome is "better" in all senses of the word. I regard Google Chrome as unmitigated spyware: It installs a persistent background app that can in turn download, install, and run code whenever it wants. When you launch Chrome, it makes connections to a wide collection of Google domains even if you have all Google services unchecked or try to set it for maximum privacy. If you block one of these connections it tries another domain. Google may argue that this behavior is necessary to traverse locked-down networks, detect man-in-the-middle, but I just see it as malware-like behavior.
I'd actually use Chrome if it made zero (0) connections to any Google property, ever, unless I explicitly hit a button that read "Check for Updates." And then I wouldn't press that button; I'd periodically download new versions of Chrome from Google itself. Because I don't trust Google not to leak some GUID back to the Googleplex during a simple update call.
Google holds the market lead for now. IE did back in 200X, then lost it because it was complacent with web standards. Google may lose it because of privacy.