Did you know that this kind of thing happens all the time — Browser 1 is popular. It implements A Cool Feature a certain way. Developers think that's correct, because it's what most users have. Browser 2 follows the web standard & implements according to the agreed-upon spec. But it's different Browser 1. And web developers make their site work in Browser 1. And so it doesn't really work correctly in Browser 2. And developers get frustrated, and blame Browser 2.
But it's Browser 1 that's wrong.
Modern web browser engines are complex beasts, and so is modern web content. The WebKit team delivered massive speedups on the Speedometer 3.0 benchmark. Here's technical deep dive into just a few of the dozens of individual optimizations.
https://webkit.org/blog/15249/optimizing-webkit-safari-for-speedometer-3-0/
Interop 2024 is here!!
https://webkit.org/blog/14955/the-web-just-gets-better-with-interop/
@scottjenson @alvaromontoro we didn’t avoid standards bodies. This has been proposed as a PR to HTML and discussed extensively there and in three related issue. https://github.com/whatwg/html/pull/9546
Just wrapped on #TheClockFilm, written by @jelena, and directed by me - starring #CCHPounder and #WallaceShawn - can’t wait to share it with you!
Safari 17.4 beta 1 came out today!
- CSS `content` alternative text syntax
- `@scope`
- `align-content` on block containers & table cells
- `white-space-collapse` and `text-wrap-mode`
- `::grammar-error` and `::spelling-error`
- form control vertical writing modes
- `<hr>` inside `<select>`
- `<input type="checkbox" switch>`
- `Promise.withResolvers`
- `TimeZoneOffset` for `Intl.DateTimeFormat`
- `ArrayBuffer.prototype.transfer`
- updated `IntlMathematicalValue`
(part 1 of 3)
Head of
@webkit
engineering at Apple. Also networking APIs. Opinions are personal unless stated otherwise.