News for hackers. Stuff that matters.
Re:WebKit Features in Safari 17.2 by infotainment on Monday December 11, 2023 @03:29PM (#38605078)
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

Re:WebKit Features in Safari 17.2 by amadeuspagel on Monday December 11, 2023 @05:27PM (#38606328)
> 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.

Re:WebKit Features in Safari 17.2 by thepra on Monday December 11, 2023 @07:31PM (#38607525)
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)
Re:WebKit Features in Safari 17.2 by nasso_dev on Tuesday December 12, 2023 @05:08PM (#38619368)
what do you use for auth if not cookies? genuinely curious
Re:WebKit Features in Safari 17.2 by thepra on Wednesday December 13, 2023 @07:44AM (#38626529)
The usual JWT Token
Re:WebKit Features in Safari 17.2 by diebeforei485 on Monday December 11, 2023 @08:30PM (#38608067)
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.
Re:WebKit Features in Safari 17.2 by amadeuspagel on Tuesday December 12, 2023 @08:31AM (#38611828)
Yes, that's also how I parsed it.
Re:WebKit Features in Safari 17.2 by diebeforei485 on Saturday December 16, 2023 @12:27AM (#38661984)
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?
Re:WebKit Features in Safari 17.2 by jensimmons on Tuesday December 12, 2023 @11:52PM (#38622821)
Correct.
Re:WebKit Features in Safari 17.2 by Aerbil313 on Monday December 11, 2023 @06:01PM (#38606704)
> 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.

Re:WebKit Features in Safari 17.2 by al_borland on Monday December 11, 2023 @07:19PM (#38607397)
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.
Re:WebKit Features in Safari 17.2 by Aerbil313 on Tuesday December 12, 2023 @07:06AM (#38611135)
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.
Re:WebKit Features in Safari 17.2 by al_borland on Tuesday December 12, 2023 @10:14PM (#38622193)
Ah, cool. Thanks for clarifying.
Re:WebKit Features in Safari 17.2 by diebeforei485 on Monday December 11, 2023 @08:06PM (#38607823)
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.