[HN Gopher] News from WWDC23: WebKit Features in Safari 17 Beta
___________________________________________________________________
News from WWDC23: WebKit Features in Safari 17 Beta
Author : itsuka
Score : 37 points
Date : 2023-06-06 12:19 UTC (10 hours ago)
(HTM) web link (webkit.org)
(TXT) w3m dump (webkit.org)
| pjmlp wrote:
| Lots of nice improvements.
| littlecranky67 wrote:
| > Web apps on Mac support web push, badging, and all the usual
| web standards implemented by WebKit, just like web apps on iOS
| and iPadOS.
|
| Not a lie, but they leave out an important part: To have webpush
| or badges on iOS you need to "install" the web app - but since
| iOS PWAs block custom install buttons, the user had to know thst
| he has to push "Share" and "Add to home screen". To my
| experience, almost noone knows this or does this.
| DANmode wrote:
| > the user had to know thst he has to push "Share" and "Add to
| home screen".
|
| So there has to be a tasteful user notification informing them
| that the site has enabled that feature in the manifest?
| chocolatkey wrote:
| Does anyone have more details on this point: "Support for Ed25519
| cryptography." ? I imagine it's part of SubtleCrypto, is it based
| on https://wicg.github.io/webcrypto-secure-curves/ ?
| kevincox wrote:
| > When a user adds a website to their Dock, Safari will copy the
| website's cookies to the web app. That way, if someone is logged
| into their account in Safari, they will remain logged in within
| the web app. This will only work if the authentication state is
| stored within cookies. Safari does not copy over any other kind
| of local storage. After a user adds a web app to the Dock, no
| other website data is shared, which is great for privacy.
|
| This seems like a strange decision.
|
| 1. Auth with local storage can be quite nice if you don't need to
| send the cookies to the server on every request.
|
| 2. This will lead to different login states in the browser and in
| the "app" which is not what I would expect and can be
| inconvenient if you open links to that website.
| littlecranky67 wrote:
| Wish they would do this on iOS (and allow a custom install
| button). They recently removed shared Caches between
| serviceworkers in Safari and the PWA on iOS, requiring to
| relogin after every PWA "install" :(
|
| As for your (2) point, I think cookies is the only thing that
| should be copied. LocalStorage or IndexedDB could result in
| inconsistwncies and breakage (PWA and Website code can version
| missmatch).
| samwillis wrote:
| Lots of really nice new stuff, particularly excited that Apple
| are finally embracing PWAs!
|
| Interesting to see Safari adding JPEG XL support just as Chrome
| dropped it:
|
| https://news.ycombinator.com/item?id=35589179
|
| https://news.ycombinator.com/item?id=33399940
| simpleintheory wrote:
| That's on Mac. PWAs on Mac aren't a new capability since Chrome
| et al have had it for a long time. I'd be more interested if
| they improved iOS PWA capabilities
| FractalHQ wrote:
| Nice now fix 3D transforms, SVG animations and clip-path or give
| me 200 hours of my life back. Safari rendering engine is a bug
| infested nightmare.
| warning26 wrote:
| You're getting downvoted but to be honest, it's true --
| Safari's layout engine and JS execution is just so glitchy and
| unpredictable. I'm guessing it's because they're prioritizing
| speed/efficiency over accuracy, but as a web dev
| it's...frustrating.
| meepmorp wrote:
| Yay, safari 17 will support profiles!
| nmstoker wrote:
| Seems like Apple got a bit more web friendly recently (esp.
| seeing web browsing demoed in Vision Pro)
___________________________________________________________________
(page generated 2023-06-06 23:02 UTC)