It’s on the technical side of things, but Apple recently detailed the 13 major WebKit changes applied in Safari 11.1 when macOS 10.13.4 High Sierra hit last week.
The changes are as follows:
Service Worker API
The Service Worker API enables scripts that run in the background to handle generalized processing for web pages. Service Worker scripts commonly work with other complimentary APIs, such as the Cache API, also included in this release, to store fetch requests and responses that to improve network performance or provide an offline experience. WebKit’s implementation respects user privacy partitioning Service Workers by the top level document origin to help prevent cross-site tracking.Read the “Workers at Your Serivce” blog post for more details about the WebKit implementation fo Service Workers.
Payment Request API for Apple Pay
WebKit added support for the Payment Request API to perform Apple Pay transactions. This enables merchants to offer payment methods across multiple browsers using a standard API, greatly reducing the effort of supporting secure payments across different browsers and platforms.See Introducing the Payment Request API for Apple Pay for more details.
Beacon API
Beacon API schedules asynchronous requests to send before the page is unloaded and completes them without a blocking request. This is useful for sending diagnostics data about the web application without impacting perceived page load performance.See the Beacon specification for more information.
Directory Upload & Clipboard API Updates
The Clipboard API has a number of improvements focusing on a modernized implementation of the DataTransfer API. It adds support for dataTransfer.items, reading and writing of HTML content and custom MIME types, and fixed a number of bugs including copying & pasting images from native applications. WebKit also added support for uploading directories using DataTransfer.webkitGetAsEntry() and input.webkitdirectory, allowing interoperability with other browsers. Users can now upload an entire directory onto cloud storage and file sharing services such as iCloud or Dropbox.Read more about the improvements to the Clipboard API and Directory Upload API.
Video as Image Assets
Animated image formats are very popular, but they easily become large, bandwidth intensive file sizes. To address the performance impact, WebKit in Safari now supports loading H.264 encoded MP4 video with an HTML tag. This allows content authors to replace animated GIF files that are much larger than H.264 video files and require more processing power to display. Beyond the performance gains, this change also allows web content authors to use videos as a CSS background-image.Some detailed information about this change is available in the blog post Evolution of : Gif without the GIF by Colin Bendell.
font-display
Page authors have more control over font loading behavior using the newly support font-display descriptor. WebKit’s new default behavior will show invisible text for up to 3 seconds before switching to an installed font until the desired font finishes downloading. Using font-display, the page author can use the swap value to immediately show an installed font until the specified web font is downloaded. There is a fallback behavior to show an installed font for up to 3 seconds and if the desired font doesn’t load in that time, it will never be shown. Finally, the optional behavior will use the font if it is available in the browser’s cache. If it isn’t there, it skips using it at all. These provide a rich set of behaviors for web developers to control the loading and display experience that best suits the design of their web content.Find more details in the CSS Fonts Module Level 4 specification.
HTMLImageElement.decode()
Content authors sometimes need a loaded, fully decoded image that is available immediately. Loading and decoding large images or lots of images can cause page performance to suffer. The new HTMLImageElement.decode() function asynchronously starts decoding an image and returns a Promise that resolves when the decoded image is available. With it, developers now have control over when loaded images are decoded, without tying up the main thread.Passive Event Listeners
To avoid causing poor scroll performance when attaching event handlers to touchstart, touchmove, or wheel events, developers can specify their event listener as passive if the listener does not call preventDefault(). This enables Safari to continue to provide high performance scrolling without waiting for the event listener to finish.More details on Passive Events Listeners can be found in the DOM specification.
Offscreen Canvas
The Offscreen Canvas API offers a mechanism to pre-render a canvas offscreen before rendering it to a visible canvas. This approach offers significant performance gains for especially complex scenes.Read more about the Offscreen Canvas API.
Storage Access API
The new Storage Access API provides a solution to allow third-party embeds to request access to their first-party cookies when the user interacts with them in a world with Intelligent Tracking Prevention. This gives content providers the flexibility to provide embedded content, while offering users transparency about who they are sharing their information with.Find out more about the Storage Access API on the WebKit blog.
Subresource Integrity
WebKit has added support for Subresource Integrity which enables websites to validate the integrity of resources and reject them if something has changed outside the site owner’s control. An integrity check compares a hash provided by the web content author in an integrity attribute on a
In short, there were muchos changes under Safari’s hood with the most recent macOS update.
Stay tuned for additional details as they become available.
Via The Mac Observer and webkit.org