Apple today released a new update for Safari Technology Preview, the experimental browser Apple first introduced over 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 58 includes the same WebKit revisions that were present in Safari Technology Preview 57, but with Safari and WebKit features that will be coming to Safari 12 when it is released later this year.
Icons in tabs, improved Intelligent Tracking Prevention, and Automatic Strong Password functionality for automatically generating unique, strong passwords when signing up for accounts or changing passwords on websites.
Today's Safari Technology Preview update is available for both macOS High Sierra and macOS Mojave, the newest version of the Mac operating system that's currently being beta tested by developers.
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
Legacy NPAPI Plug-ins
* Removed support for running legacy NPAPI plug-ins other than Adobe Flash.
Regarding the AutoFill improvements, they reference a page that gives examples, but that page is not working for me...
The suggested passwords are always 4 characters in length, regardless of the rules specified. Bug in the browser or in that web page?
EDIT - Refreshing the page gives passwords at the correct default length of 20 characters, but changing the minimum length does not adjust the length of the suggested passwords, so definitely a bug on that page.
EDIT #2 - Got it to work. Odd behaviour, but seems to be responding mostly correctly.