Safari Technology Preview 243 ships
- Apple shipped Safari Technology Preview 243 on May 7 for macOS Sequoia and Tahoe, updating its test browser with new WebKit changes developers can try now. - The build spans WebKit revisions 310600 through 312007 and adds or fixes behavior across Accessibility, CSS, JavaScript, Web APIs, WebGPU, and more. - This is the browser Apple uses to preview upcoming Safari behavior, so web teams can catch rendering and API regressions early.
Safari Technology Preview 243 is out, and this is Apple’s latest “try the future first” build for the web stack on Mac. That sounds niche, but the stakes are real — if your site, app, or web tool depends on browser behavior, these preview releases are where breakage and fixes often show up before they land in regular Safari. This one shipped on May 7, 2026, for macOS Sequoia and macOS Tahoe, and it bundles WebKit changes from revision 310600 through 312007. ### What is Safari Technology Preview? It’s Apple’s standalone test browser for upcoming Safari features. You install it next to the regular Safari app, not on top of it, and Apple uses it to expose fresh WebKit work, new platform behavior, and updated developer tooling before those changes graduate into the stable browser. ### What actually shipped in 243? The short version is breadth. (webkit.org) Apple’s release notes list updates across Accessibility, Animations, CSS, Canvas, Editing, Encoding, Forms, HTML, JavaScript, Media, Networking, PDF, Rendering, SVG, Scrolling, Spatial Web, UI, Web API, Web Inspector, WebAssembly, WebGPU, and WebRTC. That tells you this is not a single-feature drop — it’s a broad maintenance and standards-conformance pass across the engine. (developer.apple.com) ### Which fixes stand out? A few examples show the pattern. Apple fixed accessibility bugs where `contextmenu` was not firing correctly inside iframes when triggered through keyboard or assistive-tech actions, and where color picker inputs could not be activated with VoiceOver’s press action. It also fixed VoiceOver behavior for base `<select>` elements, including popover closing and positioning when CSS transforms are involved. These are the kinds of bugs that look tiny in release notes but matter a lot in real UI testing. (developer.apple.com) ### What changed in CSS? There are both new features and cleanup. Apple added support for `contain: style` applying to CSS quote counters and added the `insert` keyword for `text-autospace`. It also fixed a long list of layout and rendering issues — flex-basis definiteness, anonymous block positioning, `box-shadow` on `table-row`, `fit-content` height bugs, quirks-mode percentage sizing, `clip-path: inset` border-radius rendering, old `-webkit-box` sizing inside `fieldset`, and even performance on pages using `:where` and `:is` selectors. (webkit.org) Basically, this is exactly the kind of release frontend engineers regression-test against component libraries. ### Why mention WebGPU and Web APIs? Because those are the parts most likely to affect advanced web apps, not just ordinary page rendering. Apple’s release notes explicitly include Web API and WebGPU sections in this build, alongside JavaScript, WebAssembly, WebRTC, and Web Inspector. Even without treating every bullet as headline news, that mix signals that Apple is still tightening behavior in the APIs developers use for richer apps, graphics workloads, debugging, and cross-browser feature testing. (webkit.org) ### Who should care? Mostly web developers, browser engineers, framework maintainers, and anyone shipping complex frontends on Apple platforms. If you maintain design systems, custom controls, accessibility-heavy interfaces, graphics features, or browser-dependent workflows, STP is where you validate assumptions before the stable Safari channel moves. Apple updates it every few weeks, and the whole point is early feedback. (developer.apple.com) ### How do you get it? If you already have Safari Technology Preview installed, Apple says you can update through System Settings under General, then Software Update. New installs are available from Apple’s Safari developer resources, with separate downloads listed for macOS Tahoe and macOS Sequoia. ### Bottom line? This is not a flashy browser launch. It’s the plumbing release that tells web teams where Safari is heading next — and where subtle bugs just got fixed before they surprise users in production. (developer.apple.com 1) (developer.apple.com 2) (webkit.org)