WebKit Features in Safari 17.2

> Whether a user is in Safari, Safari View Controller, or another browser on iPhone or iPad, when they tap “Add to Home Screen” and create a web app, the cookies are copied over, including the information about login state. This will only work if the authentication state is stored within cookies. No other kind of local storage is copied over.

> After a user adds a web app to the Home Screen or Dock, no other website data is shared, which is great for privacy.

So an offline-first app will not work. A user has to login if they want to see the same data when they open a web app from the home screen and when they open the same web app from the browser, and the data has to be synced in the cloud to make that work. Great for privacy.

Wow, I hadn't heard of CSS nesting before! Definitely glad to see another of my favorite SCSS features making it into regular CSS:

https://caniuse.com/css-nesting

I've been using the Safari Web App for Slack and it's a far better experience than the Electron app that Slack distributes. Much smoother, lower battery consumption - just a win overall.

> One time codes Previously supported in Safari through other technology, the ability to have input fields that suggest received one-time codes is now available in WKWebView for iOS 17.2 and iPadOS 17.2.

One more reason not to move away from Orion. Though means nothing as screen time restrictions on websites don’t work with 3rd party browsers.