5 ms·

WebKit Features in Safari 17.4

76 points by feross 3y ago

AprilArcus 3y ago
> custom menu commands that will appear in the File menu and the Dock context menu This is pretty neat, but the "File" menu is sort of a vestige of a file-based approach to content management that isn't especially popular in the present era. Web apps aren't usually file-based (e.g. Twitter, Facebook) or aren't file-based in a way that is exposed to the PWA's API (e.g. Figma). It would be better to put these in the application menu (the bold faced one with the application name to the left of "file"). > <input type="checkbox" switch> This grieves me a bit. Because the semantics of a checkbox and switch are identical, I wish it were handled at the CSS layer and not by means of an attribute. Then you could e.g. switch from checkboxes for desktop user agents to switches for mobile UAs using a breakpoint.
- danaris 3y ago
  > It would be better to put these in the application menu (the bold faced one with the application name to the left of "file"). This is not an unreasonable proposal in itself; however, it does not conform to how Apple still treats the File menu in general, or its guidelines for its use.
dabinat 3y ago
The feature most interesting to me, that was buried a long way down, is that iOS now supports VP9 decoding. VP9 now has 97% browser support according to CanIUse and could feasibly replace H.264 as the base video codec for the web. (I know AV1 is superior but it has not achieved widespread support yet and requires hardware support on Apple platforms)
- chipweinberger 3y ago
  wow that’s a really huge feature! VP9 is pretty good.
- kiririn 3y ago
  VP9 has been available, at least in HLS streams, since iOS 14. If there is anything new here it is support for a new container format I’m always surprised VP9 isn’t more widely used and that people seem to want to jump straight to AV1. For any video for web delivery where I control the codec end to end I always choose VP9
danaris 3y ago
Aside from the VP9 support and switch checkboxes, which others have mentioned, I'm particularly interested in the "Align content everywhere" feature, allowing you to use div { align-content: center; } to get nice center-aligned content without having to use flexbox or grid.
CM30 3y ago
Seems like a few interesting features to me. Shortcuts and categories definitely improve the PWA experience a bit, so they should be useful there. The switch control is long overdue, though it might be better if they standardised the styling options for ALL input elements first, since too many of them are hard to style consistently across browsers right now without using browser specific selectors. Vertical form controls are useful, and seem like a logical inclusion. And align content inside block elements... damn, that's something that really should have been in browsers from the get go. Might finally kill the memes about centering text in CSS!
jacobp100 3y ago
Glad to hear they’re rewriting their flexbox algos. Both Chrome and Safari had a huge number of issues around a decade ago, but Chrome managed to rewrite their engine and now has a very good engine. Safari was lagging behind a lot here, so it’s really welcome news
CharlesW 3y ago
> "We built two new iOS frameworks with hundreds of new APIs to support functionality used by web browsers, including multiprocess, JIT, and advanced keyboard & touch event access — and we are pivoting WebKit to use these new frameworks." "Used by web browsers" implies that these APIs were designed to be used by both 3rd-party rendering engines and WebKit, which is interesting. It would mean that Apple's been building OS infra for 3rd-party browsers for many years.
- lapcat 3y ago
  They could just mean in-app browsers, which use WebKit.
siproprio 3y ago
What about better adblocking? As soon as Firefox hits the stores I’ll be switching.
- olliej 3y ago
  There are plenty of adblockers for safari that work fine?
- Terretta 3y ago
  > What about better adblocking? As soon as Firefox hits the stores I’ll be switching. Then why haven't you tried Kagi's Orion which supports Firefox extensions? https://kagi.com/orion/ https://kagi.com/orion/ See the “privacy by design” privacy comparison matrix down the page. // See also 1Blocker and AdGuard for Safari and MacOS/iOS.
- graftak 3y ago
  I use 1blocker and ad blocking has been pretty much flawless. The native code precompiled manifest way of content filtering is more performant and efficient too.
hwbunny 3y ago
media query fullscreen ETA?
miragecraft 3y ago
Really happy to see @scope is now here, though with Firefox dragging their feet (like they have with :has() and still are with @property) it still won't be usable anytime soon.

76 points by feross 3y ago

> custom menu commands that will appear in the File menu and the Dock context menu This is pretty neat, but the "File" menu is sort of a vestige of a file-based approach to content management that isn't especially popular in the present era. Web apps aren't usually file-based (e.g. Twitter, Facebook) or aren't file-based in a way that is exposed to the PWA's API (e.g. Figma). It would be better to put these in the application menu (the bold faced one with the application name to the left of "file"). > <input type="checkbox" switch> This grieves me a bit. Because the semantics of a checkbox and switch are identical, I wish it were handled at the CSS layer and not by means of an attribute. Then you could e.g. switch from checkboxes for desktop user agents to switches for mobile UAs using a breakpoint.

danaris 3y ago
> It would be better to put these in the application menu (the bold faced one with the application name to the left of "file"). This is not an unreasonable proposal in itself; however, it does not conform to how Apple still treats the File menu in general, or its guidelines for its use.

dabinat 3y ago

The feature most interesting to me, that was buried a long way down, is that iOS now supports VP9 decoding. VP9 now has 97% browser support according to CanIUse and could feasibly replace H.264 as the base video codec for the web. (I know AV1 is superior but it has not achieved widespread support yet and requires hardware support on Apple platforms)

chipweinberger 3y ago
wow that’s a really huge feature! VP9 is pretty good.
kiririn 3y ago
VP9 has been available, at least in HLS streams, since iOS 14. If there is anything new here it is support for a new container format I’m always surprised VP9 isn’t more widely used and that people seem to want to jump straight to AV1. For any video for web delivery where I control the codec end to end I always choose VP9

danaris 3y ago

Aside from the VP9 support and switch checkboxes, which others have mentioned, I'm particularly interested in the "Align content everywhere" feature, allowing you to use div { align-content: center; } to get nice center-aligned content without having to use flexbox or grid.

CM30 3y ago

Seems like a few interesting features to me. Shortcuts and categories definitely improve the PWA experience a bit, so they should be useful there. The switch control is long overdue, though it might be better if they standardised the styling options for ALL input elements first, since too many of them are hard to style consistently across browsers right now without using browser specific selectors. Vertical form controls are useful, and seem like a logical inclusion. And align content inside block elements... damn, that's something that really should have been in browsers from the get go. Might finally kill the memes about centering text in CSS!

jacobp100 3y ago

Glad to hear they’re rewriting their flexbox algos. Both Chrome and Safari had a huge number of issues around a decade ago, but Chrome managed to rewrite their engine and now has a very good engine. Safari was lagging behind a lot here, so it’s really welcome news

CharlesW 3y ago

> "We built two new iOS frameworks with hundreds of new APIs to support functionality used by web browsers, including multiprocess, JIT, and advanced keyboard & touch event access — and we are pivoting WebKit to use these new frameworks." "Used by web browsers" implies that these APIs were designed to be used by both 3rd-party rendering engines and WebKit, which is interesting. It would mean that Apple's been building OS infra for 3rd-party browsers for many years.

lapcat 3y ago
They could just mean in-app browsers, which use WebKit.

siproprio 3y ago

What about better adblocking? As soon as Firefox hits the stores I’ll be switching.

olliej 3y ago
There are plenty of adblockers for safari that work fine?
Terretta 3y ago
> What about better adblocking? As soon as Firefox hits the stores I’ll be switching. Then why haven't you tried Kagi's Orion which supports Firefox extensions? https://kagi.com/orion/ https://kagi.com/orion/ See the “privacy by design” privacy comparison matrix down the page. // See also 1Blocker and AdGuard for Safari and MacOS/iOS.
graftak 3y ago
I use 1blocker and ad blocking has been pretty much flawless. The native code precompiled manifest way of content filtering is more performant and efficient too.

hwbunny 3y ago

media query fullscreen ETA?

miragecraft 3y ago

Really happy to see @scope is now here, though with Firefox dragging their feet (like they have with :has() and still are with @property) it still won't be usable anytime soon.