Apple's WebKit team on November 18, 2026 published release notes for Safari Technology Preview 257, an experimental build of Safari for macOS Golden Gate and macOS Tahoe that lists 201 changes to the browser engine. Ten are new features. The remaining 191 are fixes, and a small group of them sits in the plumbing that analytics scripts, ad tags and privacy extensions rely on: requests sent as a page closes, the timing entries a page records for its iframes, and the rules extensions use to remove parameters from URLs.

The most direct of them for measurement is a single line under Networking. "Fixed beacons sent from pagehide being lost when a page is closed and its process shuts down," according to the notes.

In Short

Apple released a test version of Safari on November 18 with 201 changes, including a fix for data that websites try to send at the moment a page is closed, which was being lost. That matters to anyone measuring websites in Safari, because analytics and ad scripts often send their final report as a visitor leaves, and to makers of privacy extensions that remove tracking parameters from links. The notes do not say when any of these changes will reach the Safari that people use every day, so for now they show what Apple's engine team has fixed, not what has shipped.

A test browser with a long version history

Safari Technology Preview is the build in which Apple ships WebKit engine work before it reaches the regular browser. The notes link its name to WebKit's original post introducing the program, and when PPC Land covered Safari Technology Preview 192 in April 2024, it described the release as a glimpse of where Apple's production browser was heading and noted that it installs alongside regular Safari. Sixty-five numbered releases separate that build from this one (PPC Land calculation).

Release 257 is signed by Saron Yitbarek. According to the notes, it includes WebKit changes between 324654@main and 326096@main, and that range links to a comparison of two commits in WebKit's public GitHub repository. The span covers 1,442 commit numbers (PPC Land calculation). Each of the 201 entries carries its own commit identifier, linked to commits.webkit.org, and a second reference number in parentheses that the notes do not explain.

Most of the release is unglamorous. CSS alone accounts for 51 fixes, many of them about flexbox and grid sizing. Three separate entries correct flex layouts that ended "up to 1/64 of a pixel short of the end edge" of their containers. Web Extensions is the second-largest category, with 31 entries, followed by Web API with 29.

How the release is distributed

According to the notes, the build reaches developers in the following way:

  1. The release is available for two operating systems: macOS Golden Gate and macOS Tahoe. No iPhone, iPad or Vision Pro build is mentioned.
  2. Machines that already have Safari Technology Preview installed receive the update through System Settings, under General, then Software Update.
  3. New installations start from Apple's Safari resources page for developers, which the notes link from the words "available for download."
  4. Each entry links to its commit on commits.webkit.org, so a developer can read the code change behind any line in the notes.

The last request before a page closes

The beacon fix is short, and its wording is precise about the conditions. Two things had to happen together for the data to disappear: the page was closed, and the process running it shut down. In that case, beacons sent from the pagehide event were lost.

Pagehide is the event a browser fires when it leaves a page, including when a tab is closed. A beacon is a small request designed to leave the browser at exactly that moment, without holding up navigation. Analytics libraries and the tracking pixel calls that ad platforms use for measurement often rely on that window to send the last piece of a session: engagement time, final scroll depth, an exit event. If the browser tears down the process before those requests go out, the session ends without them, and the report arrives incomplete.

How many sessions ended without their final beacon? The notes do not say. They give no share of beacons lost, no indication of how long the bug existed, and no statement on whether shipping versions of Safari behave the same way. They also do not name the specific web interface involved. What they establish is narrower: in Technology Preview 257, WebKit treats the loss as a bug and says it has been fixed.

For marketers, the timing is notable. Most of the Safari stories that have reached advertisers this year have been about Apple choosing to limit measurement, through Intelligent Tracking Prevention, the Safari 27 block on The Trade Desk's adsrvr.org domain, or the block on identity firms that turn email addresses into tracking IDs. The pagehide fix belongs to a different category: data that a page tried to send and that the browser dropped by accident.

Every iframe navigation, now on the record

A second measurement change sits under Web API. "Fixed an issue where only the first navigation of an iframe was reported in the parent document's Resource Timing entries. Every navigation initiated by the parent document is now reported," according to the notes.

Resource Timing is the browser interface that records how long each resource on a page took to load. Performance monitoring tools read it to find slow third parties, and iframes are where much of that third-party content lives. When PPC Land reported in September that Chrome had put publishers' ad loads on public record with four new metrics, the coverage noted that most ads run in cross-origin iframes, which is why the measurement has to happen inside the browser.

Under the old behavior in WebKit, a parent page that pointed an iframe at a new address would see only the first load in its timing data. The fix covers navigations "initiated by the parent document." Navigations an iframe starts on its own, such as a redirect from inside the frame, fall outside that wording, and the notes do not address them.

Two smaller entries touch the same area. A fix to Cache's match() and matchAll() means they now "queue Reporting API Cross-Origin-Resource-Policy violation reports when a cross-origin opaque response is blocked." And ReportingObserver reports and their bodies are now "plain objects, so they can be structured-cloned and posted," with their toJSON() methods removed. A separate fix stops ReportingObserver from invoking its callback with no reports after takeRecords() was called.

One Networking entry changes how Safari treats hints sent by servers. "Fixed Link response headers on subresources (such as CSS, scripts, and fonts) incorrectly triggering rel=preload and rel=preconnect. Only the main resource now does," according to the notes.

Preload and preconnect tell a browser to fetch a file early or to open a connection to a server before it is needed. In the old behavior, a script or stylesheet served by a third party could carry such a hint in its HTTP headers, and WebKit would act on it. In Technology Preview 257, only the hints on the page's own main document count. The notes describe the earlier behavior as incorrect, so any vendor that benefited from it in Safari was relying on a bug.

Two further entries are relevant to the scripts that tag managers and analytics libraries schedule. requestIdleCallback no longer drops its timeout "when the callback was already in the list of runnable idle callbacks." And window.print() no longer waits for active XMLHttpRequest requests, "such as long-polling," to finish before showing the print dialog.

Extensions and the rules that rewrite URLs

The Web Extensions section matters to a different audience: the developers of content blockers and privacy tools, and the advertisers whose links pass through them.

Safari extensions can declare rules through an interface called declarativeNetRequest, which the browser applies to network requests on the extension's behalf. Those rules are bounded by the browser extension permissions each extension declares in its manifest. One of the actions a rule can take is a redirect that rewrites the URL, and one form of rewrite, queryTransform.removeParams, deletes named query parameters from it.

Technology Preview 257 fixes how several of those rules combine. According to the notes, it "Fixed declarativeNetRequest redirect rules of equal priority from the same extension that only remove query parameters with queryTransform.removeParams so they all apply instead of only the first."

Read literally, an extension that defined one rule per parameter at the same priority would, before this build, have stripped only one of them from a matching URL. In 257, all of them apply. The notes name no parameters and no extensions. For paid search, the parameters most often discussed in this context are click identifiers such as the GCLID that Google Ads appends to each ad click, which is how conversions are tied back to a click. Safari's own protections already strip it in some modes: PPC Land's testing of the iOS 26 beta in September 2025 found gclid intact in regular browsing but removed when protection for all browsing was switched on manually and for links opened from Mail and Messages, and an April 2026 estimate put the stripping at roughly 20% of sessions under Private Browsing's default protection. Extensions are a separate layer on top of that, and this fix makes their parameter rules behave as written.

Three other declarativeNetRequest entries point the same way:

  • modifyHeaders rules no longer reject custom header names.
  • The quota check for updateDynamicRules and updateSessionRules no longer counts existing rules twice, so extensions are no longer refused before reaching their actual limit.
  • declarativeNetRequest.ResourceType is now one of the enum types added to the browser.* namespaces, alongside cookies.SameSiteStatus, extension.ViewType and menus.ContextType.

Other extension entries tighten security. tabs.update() no longer allows extensions "to navigate a tab to javascript: URLs, or to file: URLs when the extension does not have file access." tabs.connect() no longer also connects to "the opener or opened window of the target tab." A Content-Security-Policy-Report-Only header, which is meant to report violations without enforcing them, had been "incorrectly blocking Safari extension scripts from loading," and that is fixed. alarms.create() now rejects alarm names longer than 1,024 bytes and new alarms once an extension has 500.

The new extension features are developer conveniences. Manifests can now declare "message_serialization": "structured_clone", so messages sent with runtime.sendMessage() "can carry values such as ArrayBuffer and Blob between content scripts and the background page." A windowId property has been added to runtime.MessageSender. And WebKit fixed "excessive memory use in web extensions by registering each event listener only once and delivering runtime and port messages without keeping a copy per listener."

Privacy, identity and sandboxing

Several entries concern what a page can hold on to and what it can prove.

  • Cache clearing. "Fixed removing disk cache data not canceling pending cache writes." Before the fix, removing cached data did not stop writes already in progress. The notes do not say which data was affected or how long such writes could take.
  • Sandboxed frames. "Fixed events not being dispatched to nodes inside a sandboxed iframe." The notes do not say which events or which sandbox settings were involved.
  • Enhanced Security. A fragment-only, same-document navigation "could trigger a page reload when Enhanced Security is enabled." That is fixed.
  • Blob workers. A dedicated worker started from a blob URL that was revoked immediately had been getting "a new opaque origin," which blocked it from reading Blob objects or importing other blob URLs.
  • Digital credentials. navigator.credentials.get() had been "dropping OpenID4VP requests when a page also offered an org-iso-mdoc request; all requests are now presented together." WebKit introduced the Digital Credentials API for Safari 26 in October 2025, and PPC Land's coverage at the time described mdoc-based identity documents and the ability of sites to verify age attributes through it.
  • Passkey sign-in. A new feature adds "support for the WebAuthn cross-device fallback URL extension." WebAuthn is the standard behind the passkey, the device-bound key pair used in place of a password. The notes give no further detail on the extension's behavior.
  • Cryptography. SubtleCrypto.deriveBits() now enforces "the range of its length argument, as the specification requires."

Video that keeps playing

For advertisers running video in display placements, the Media section has two entries of note. "Fixed muted autoplaying looping WebM video stopping playback at the second loop boundary," according to the notes. Muted autoplay is the configuration browsers allow to start without a user gesture, which is why short muted loops are widely used for motion in display creative and on product pages. A loop that halted at its second pass would have cut such a clip short.

The second is "Fixed inline videos sometimes showing a black screen after playing while off-screen." A video that played while scrolled out of view could show black when it came back. Other media fixes address readyState not returning to HAVE_METADATA after seeking to an unbuffered position, "which caused playback to stall after scrubbing," captions overlapped by controls on sites that use video.js, audio served as application/ogg over HTTP failing to play on macOS, and a WebCodecs VideoEncoder that accepted a zero bitrate.

Rendering, and a follow-up on dark mode

One Performance entry connects to a feature PPC Land covered two weeks ago. WebKit "Fixed slow rendering and laggy scrolling on pages with many gradients affected by Adaptive Dark Mode color filters." Adaptive Dark Mode, introduced on November 3 for the Safari 27.3 beta, repaints light websites dark without the sites knowing. The fix suggests the color filters carried a performance cost on gradient-heavy pages, though the notes give no measurements.

Other performance fixes address "sluggish, stuttering scrolling on 60Hz Mac displays" and "high memory usage from elements with will-change that cover a very large area by limiting the compositing layers created for them." Scrolling to the edge of a document on macOS is now animated with a spring animation, one of the ten new features.

A handful of rendering changes affect what scripts read from a page. getComputedStyle() again includes text zoom in the font-size value it returns. Printing now lays out page content "at 96 CSS pixels per inch instead of 90, matching the CSS specification." Viewport units such as vw and vh no longer grow and squish page content during two-finger zoom on macOS. And the text selection highlight, which was not visible "on some pages, such as github.com," is fixed.

Selected entries for measurement, privacy and extensions

The table below records the entries discussed above as WebKit worded them. Apostrophes and quotation marks are normalized to straight characters.

Category Entry Commit
Networking Fixed beacons sent from pagehide being lost when a page is closed and its process shuts down. 325866@main
Web API Fixed an issue where only the first navigation of an iframe was reported in the parent document's Resource Timing entries. Every navigation initiated by the parent document is now reported. 325284@main
Networking Fixed Link response headers on subresources (such as CSS, scripts, and fonts) incorrectly triggering rel=preload and rel=preconnect. Only the main resource now does. 325035@main
Networking Fixed removing disk cache data not canceling pending cache writes. 325116@main
Networking Fixed Cache's match() and matchAll() to queue Reporting API Cross-Origin-Resource-Policy violation reports when a cross-origin opaque response is blocked. 325722@main
Web API Fixed requestIdleCallback dropping the timeout when the callback was already in the list of runnable idle callbacks. 325318@main
Web API Fixed events not being dispatched to nodes inside a sandboxed iframe. 325977@main
Web API Fixed navigator.credentials.get() dropping OpenID4VP requests when a page also offered an org-iso-mdoc request; all requests are now presented together. 325322@main
Web Extensions Fixed declarativeNetRequest redirect rules of equal priority from the same extension that only remove query parameters with queryTransform.removeParams so they all apply instead of only the first. 325510@main
Web Extensions Fixed declarativeNetRequest modifyHeaders rules rejecting custom header names. 325082@main
Web Extensions Fixed the declarativeNetRequest quota check for updateDynamicRules and updateSessionRules counting existing rules twice. 325096@main
Web Extensions Fixed tabs.update() allowing web extensions to navigate a tab to javascript: URLs, or to file: URLs when the extension does not have file access. 325101@main
Media Fixed muted autoplaying looping WebM video stopping playback at the second loop boundary. 324855@main
Media Fixed inline videos sometimes showing a black screen after playing while off-screen. 325855@main
Performance Fixed slow rendering and laggy scrolling on pages with many gradients affected by Adaptive Dark Mode color filters. 324781@main

The ten new features

Category New feature, as worded by WebKit Commit
Forms Added support for rendering <select multiple size="1"> as a dropdown box on macOS. 325870@main
Forms Added preview support, off by default, for the enhanced <select> element with the multiple attribute and list box rendering, and for cloning every selected option into selectedcontent elements. 326015@main
Scrolling Scrolling to the edge of the document on macOS is now animated with a spring animation. 325876@main
Web API Added AudioWorklet.port and AudioWorkletGlobalScope.port, allowing a page and its audio worklet to exchange messages without creating a processor node. 325762@main
Web API Added support for the WebAuthn cross-device fallback URL extension. 324658@main
Web Extensions Added a warning when a manifest V2 extension defines action without browser_action, or a manifest V3 extension defines browser_action without action. 324852@main
Web Extensions Added enum types such as cookies.SameSiteStatus, declarativeNetRequest.ResourceType, extension.ViewType, and menus.ContextType to the browser.* namespaces. 324948@main
Web Extensions Added a windowId property to runtime.MessageSender. 325024@main
Web Extensions Added support for "message_serialization": "structured_clone" in the extension manifest, so messages sent with runtime.sendMessage() can carry values such as ArrayBuffer and Blob between content scripts and the background page. 325948@main
WebGPU Added support for dual-source blending in WebGPU. 325793@main

Changes by category

Counts are PPC Land's tally of the entries in the notes.

Category New features Resolved issues Total
Animations 0 4 4
CSS 0 51 51
Canvas 0 7 7
Editing 0 1 1
Forms 2 6 8
Images 0 2 2
JavaScript 0 2 2
Media 0 11 11
Networking 0 6 6
Performance 0 3 3
Rendering 0 11 11
SVG 0 8 8
Scrolling 1 0 1
Security 0 1 1
Web API 2 27 29
Web Extensions 4 27 31
Web Inspector 0 9 9
WebAssembly 0 3 3
WebDriver 0 3 3
WebGL 0 2 2
WebGPU 1 5 6
WebRTC 0 2 2
Total 10 191 201

Global Privacy Control sits outside this release

The release notes page links, as WebKit's next blog post, to a separate article titled "Global Privacy Control (GPC) WebKit API." GPC does not appear among the 201 entries in Technology Preview 257, and the release notes say nothing about it. PPC Land covers the GPC post separately.

What has not changed in this build

Read against this year's Safari coverage, the notes are as notable for their silences. In July, PPC Land reported that the Safari 27 beta cuts connections to LinkedIn and Bing ad servers by IP address. In October, ID5's chief executive said regulators should look at Apple's iOS 27 Safari block, and Safari 27.2 dropped a mistaken seven-day cap on cookies set by CNAME-hosted sites. Technology Preview 257 contains no entry on tracking prevention, cookie lifetimes, blocked domains, link tracking protection or fingerprinting. The changes in it that affect measurement are mechanical: data that should have been sent, timing that should have been recorded, extension rules that should have applied.

What the notes do not say

The notes give no date or version number for when any of these changes will reach Safari on macOS, iOS, iPadOS or visionOS, and the build itself covers macOS only. None of the fixes comes with a figure on how often the bug occurred. Four Canvas entries carry commit identifiers between 329203@main and 330047@main, above the 326096@main end of the range the notes state, and the notes do not explain why. The second reference number on each entry is not defined.

Key facts

  • Source: "Release Notes for Safari Technology Preview 257," WebKit blog, dated November 18, 2026, by Saron Yitbarek. URL: https://webkit.org/blog/18652/release-notes-for-safari-technology-preview-257/
  • Product: Safari Technology Preview, release 257
  • Platforms: macOS Golden Gate and macOS Tahoe
  • Update path: System Settings, General, Software Update, for existing installations
  • WebKit range: 324654@main to 326096@main (1,442 commit numbers, PPC Land calculation)
  • Entries: 201 in 22 categories, of which 10 new features and 191 resolved issues (PPC Land count)
  • Largest categories: CSS (51), Web Extensions (31), Web API (29)
  • Beacon fix: 325866@main (191507608)
  • Resource Timing iframe fix: 325284@main (191225392)
  • Link header fix: 325035@main (191196085)
  • removeParams rule fix: 325510@main (191496188)
  • Digital credentials fix: 325322@main (191358037)
  • WebAuthn cross-device fallback URL extension: 324658@main (190635008)
  • Commit identifiers outside the stated range: 329203@main, 329548@main, 329650@main, 330047@main (all Canvas)
  • Adjacent WebKit posts: next, "Global Privacy Control (GPC) WebKit API"; previous, "Introducing spatial CSS: A developer preview"

Timeline

Summary

Who: Apple's WebKit team, which develops the engine behind Safari, in release notes signed by Saron Yitbarek. The changes affect website owners, analytics and ad tech vendors that measure Safari traffic, and developers of Safari extensions, including content blockers.

What: Safari Technology Preview 257, an experimental Safari build with 201 listed changes: 10 new features and 191 fixes. Among them are fixes for beacons sent from pagehide being lost when a page closes and its process shuts down, for iframe navigations missing from Resource Timing entries, for Link headers on subresources triggering preload and preconnect, and for extension rules that remove URL query parameters applying only the first of several.

When: The release notes are dated November 18, 2026. They give no date for when the changes will reach regular Safari.

Where: The build runs on macOS Golden Gate and macOS Tahoe. The notes were published on the WebKit blog, and each entry links to its commit in WebKit's public repository.

Why: Technology Preview builds are where WebKit engine changes appear before they reach Safari. For marketers, this release matters less for any new privacy restriction, of which it contains none, than for fixes to the mechanics of measurement: data a page sends as it closes, the timing record of iframes, and how extensions rewrite the links that carry campaign and click parameters.