RE: https://front-end.social/@jensimmons/115708071675176381
Safari 26.2 brings some long-awaited updates for Safari Web Extensions.
1. If you’re still shipping a Safari App Extension on Mac, during an update you can replace it with a Safari Web Extensions and KEEP the website access permissions that have already been granted. Updating to a Safari Web Extension is seamless for your users and opens up a ton of new APIs alongside the ability to ship one extension across macOS, iOS, iPadOS, and visionOS.
2. From the native app shipped with your extension, you can check if the extension has been turned on. This lets you conditionally change the contents or functionality of your app.
3. On iOS, iPadOS, and visionOS, you can now deep link your users to Safari Extension Settings. If you’re shipping one extension, you can deep link directly to it, if you ship multiple extensions, you can choose to highlight them all in Settings.
Read about all of these changes and more on WebKit.org and reach out with any feedback.
Safari 26 supports the W3C Digital Credentials API, letting users verify their identity with mobile IDs from Apple Wallet—no more uploading photos of driver's licenses!
Check out WebKit's guide covering the JavaScript API and security best practices.
https://webkit.org/blog/17431/online-identity-verification-with-the-digital-credentials-api/
The WebKit blog talks about "Rolling the Dice with CSS random()". CSS random() is a new function to generate random values for CSS properties opening up a lot of possibilities with procedurally generated layouts. Learn more from the WebKit team.
https://webkit.org/blog/17285/rolling-the-dice-with-css-random/
New WebKit post! “A gentle introduction to anchor positioning”
Anchor positioning allows you to place an element on the page based on where another element is. It makes it easier to create responsive menus and tooltips with less code using only CSS. You can read the blog post to learn how it works.
https://www.webkit.org/blog/17240/a-gentle-introduction-to-anchor-positioning/
@tareef Oh I missed this somehow.
It's mostly about the significant custom tooling and process added to it over years of use. The loss of certain productivity flows makes for a very high bar when considering switching to another platform.