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

safaripreviewicon 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 68 includes bug fixes and feature improvements for Web API, WebRTC, Media, CSS, Rendering, JavaScript, Web Inspector, WebDriver, Payment Request, Apple Pay, Web Animations, and WebCrypto.

The new Safari Technology Preview update is available for both macOS High Sierra and macOS Mojave, the newest version of the Mac operating system that was released to the public in September.

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

skunkworker

85 months ago

* Added VP8 support to WebRTC

This is a pretty big deal for Apple to finally add this.

Score: 5 Votes (Like | Disagree)

andrewsipes

Added `prefers-color-scheme` media query support for styling dark mode content

Yay, dark mode for the web!

Score: 4 Votes (Like | Disagree)

Vashetti

489 out of 555 with all experimental features enabled, up from 484 in the last version.

Score: 2 Votes (Like | Disagree)

JesperA

I wonder if that will finally enable 4K YouTube support in Safari in future, would be nice

Score: 1 Votes (Like | Disagree)

Ritsuka

Nope, Youtube uses VP9, not VP8. And VP8 is not hardware accelerated on macOS, so using it with WebRTC will actually uses more power. I guess it's fine as a fallback if the other end doesn't support h.264.

Read All Comments