Apple has a private CSS property to add Liquid Glass effects to web content

Post by move-on-by » Tue, Sep 16, 2025, 1:45 AM UTC

paradox460 wrote: post #131

senkora wrote: post #13

Earlier quoted context omitted.

Yeah, this seems reasonable to me. The better thing to get annoyed at Apple for is being slow to implement web standards. I guess you could make the argument that they are choosing to work on stuff like this instead, but I think that’s a weak argument.

And even then, they've made efforts to get better. Safari is starting to edge out Firefox for support of the features I actually want to use

Post by georgeburdell » Tue, Sep 16, 2025, 2:52 AM UTC

dham wrote: post #140

ericmcer wrote: post #137

Earlier quoted context omitted.

Its a toss up between anticompetitive being bad and unified standards being good. Look at the m3/4 macs they are insane machines because even the hardware is unified.

What do you mean by unified? Strix Halo is "unified". The M series platform isn't the only unified platform out there.

Post by JimDabell » Tue, Sep 16, 2025, 5:27 AM UTC

monocularvision wrote: post #146

JimDabell wrote: post #73

Earlier quoted context omitted.

That would not get through the App Store review process.

Depends on how you implement it.

Post by [deleted] » Tue, Sep 16, 2025, 5:37 AM UTC

cosmic_cheese wrote: post #96

bigyabai wrote: post #79

Earlier quoted context omitted.

So when Google creates self-serving APIs in a web browser engine, it's anti-consumer and is killing the free web. But when Apple creates self-serving APIs in a web browser engine, it's just another private entitlement, a red herring and their right as the proprietor of Safari. The lady doth protest too much, methinks.

The difference is that Google is by far in a much more dominant position and every dev who leverages Chrome-specific APIs further entrenches that dominance. In the browser space, Apple is the long-trailing runner-up and has far less impact. It appears that this particular API is restricted to embedded webviews, too (doesn’t work in Safari), so it has no bearing on the open web, unlike APIs such as WebUSB in Chrome.

Post by galad87 » Tue, Sep 16, 2025, 7:38 AM UTC

olivia-banks wrote: post #150

galad87 wrote: post #36

Earlier quoted context omitted.

Actually it does not. It used to, but then was rewritten. The Accessibility Inspector app can be used to see what's the class of the UI elements, if you want to check.

I think it still might. I use it all the time on my laptop, and periodically if I do something funky with the network, the entire view panel says that there was an internal server error in that classic no-CSS Times New Roman font. Do you have a source for this?