> It stands to reason that Apple wouldn't have developed this feature if they weren't using it. Where? We have no idea. But they must be using it somewhere . The fact that none of us have noticed exactly where suggests that we're interacting with webviews in our daily use of iOS without ever even realising it. This is what stood out to me. I've never really suspected webviews and can't think of a place now.
Apple has a private CSS property to add Liquid Glass effects to web content
31–40 of 208 posts
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#32Providing an OS feature only to first-party programs is a plainly anticompetitive practice. Using your privileged position in one market (cell phones/cell phone operating systems) to gain an advantage in another market (smart phone applications) that you withhold from your competitors is a textbook case.
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#33Let's pray this liquid jelly doesnt become a trend
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#34Apple's new glass UI seems to draw a lot of ire, but I... kinda like it? It feels like the OS has some actual personality again instead of just being flat and boring. I can visually tell the size of click targets now and the buttons are finally visually distinct from text again. I view it as a welcome change. It's not just "nostalgia" either. It has actual utility.
I installed the iOS 26 Beta to test some things on the websites I maintain in advance of it going public, and while there are some issues here and there I think the overall direction to add more personality back into the OS is a good one. Normies will love it.
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#35Providing an OS feature only to first-party programs is a plainly anticompetitive practice. Using your privileged position in one market (cell phones/cell phone operating systems) to gain an advantage in another market (smart phone applications) that you withhold from your competitors is a textbook case.
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#36> It stands to reason that Apple wouldn't have developed this feature if they weren't using it. Where? We have no idea. But they must be using it somewhere . The fact that none of us have noticed exactly where suggests that we're interacting with webviews in our daily use of iOS without ever even realising it. This is what stood out to me. I've never really suspected webviews and can't think of a place now.
I’m fairly certain Apple Music makes pretty heavy use of webviews.
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#37Re: Apple has a private CSS property to add Liquid Glass effects to web content
#38Earlier quoted context omitted.
Shouldn’t this be easily available in Electron/Tauri and React Native apps?
Electron doesn't use WebKit, so definitely not. Not sure about Tauri desktop, but how would you use it for Tauri mobile and React Native?
So, if you wanted webviews that could leverage this you’d basically need a native swift app with webviews to get access.
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#39Earlier quoted context omitted.
Private/secret APIs in DOS/Windows were a prominent part of the US and EU antitrust lawsuits against Microsoft in the 90s/00s.
> Private/secret APIs in Windows were a prominent part of the US and EU antitrust lawsuits against Microsoft in the 90s/00s. It mattered because Microsoft had 95% of the operating system market at the time and was using its monopoly position to take over the web, even after signing a decent decree with the US government.
The current web monopolist (Google) was coincidentally founded 2 months after the US antitrust lawsuit against Microsoft was decided (july - september 1998).
Similarly meh results with US vs Google two weeks ago.
Re: Apple has a private CSS property to add Liquid Glass effects to web content
#40Providing an OS feature only to first-party programs is a plainly anticompetitive practice. Using your privileged position in one market (cell phones/cell phone operating systems) to gain an advantage in another market (smart phone applications) that you withhold from your competitors is a textbook case.
Is Google's "-webkit-tap-highlight-color" also anticompetitive? Should we ban the current practice of shipping proprietary CSS attributes while sometimes also proposing them for standardization?
It's just really hard for me to read that as a legit complaint.