4 ms·

WebKit Features in Safari 17.2

58 points by feross 3y ago

infotainment 3y ago
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 https://caniuse.com/css-nesting
amadeuspagel 3y ago
> 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.
- thepra 3y ago
  Yep, as a web app developer I can't see what that has to do with privacy, it'll just slightly annoy the user into redoing the login within the new home shortcut(I don't use cookies for Auth)
  - nasso_dev 3y ago
    what do you use for auth if not cookies? genuinely curious
    - thepra 3y ago
      The usual JWT Token
- diebeforei485 3y ago
  I parsed that sentence as - the separate web app gets its own cookie jar, and it's pre-populated with whatever cookies existed for that website in the browser at the time the user created the separate web app, but from that point forward nothing is shared between browser and web app.
  - amadeuspagel 3y ago
    Yes, that's also how I parsed it.
    - diebeforei485 3y ago
      Because the browser login cookies would transfer to the web app, why would they have to log in again when they open the web app?
  - jensimmons 3y ago
    Correct.
Aerbil313 3y ago
> 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.
- al_borland 3y ago
  Why is this a bad feature? I quite like not having to jump back and forth between my browser and messages when I get a 2FA code.
  - Aerbil313 3y ago
    You completely misunderstood. Previously this wasn’t supported in Orion, and this was a reason to use Safari instead of other browsers. Now this reason no longer exists. I’m all for it.
    - al_borland 3y ago
      Ah, cool. Thanks for clarifying.
diebeforei485 3y ago
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.

58 points by feross 3y ago

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 https://caniuse.com/css-nesting

amadeuspagel 3y ago

> 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.

thepra 3y ago
Yep, as a web app developer I can't see what that has to do with privacy, it'll just slightly annoy the user into redoing the login within the new home shortcut(I don't use cookies for Auth)
- nasso_dev 3y ago
  what do you use for auth if not cookies? genuinely curious
  - thepra 3y ago
    The usual JWT Token
diebeforei485 3y ago
I parsed that sentence as - the separate web app gets its own cookie jar, and it's pre-populated with whatever cookies existed for that website in the browser at the time the user created the separate web app, but from that point forward nothing is shared between browser and web app.
- amadeuspagel 3y ago
  Yes, that's also how I parsed it.
  - diebeforei485 3y ago
    Because the browser login cookies would transfer to the web app, why would they have to log in again when they open the web app?
- jensimmons 3y ago
  Correct.

Aerbil313 3y ago

> 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.

al_borland 3y ago
Why is this a bad feature? I quite like not having to jump back and forth between my browser and messages when I get a 2FA code.
- Aerbil313 3y ago
  You completely misunderstood. Previously this wasn’t supported in Orion, and this was a reason to use Safari instead of other browsers. Now this reason no longer exists. I’m all for it.
  - al_borland 3y ago
    Ah, cool. Thanks for clarifying.

diebeforei485 3y ago

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.