iOS 26.3 and macOS 26.3 Fix Dozens of Vulnerabilities, Including Zero-Day
macrumors.com
macrumors.com
My hope was that Apple would be forced to course correct in subsequent releases but that doesn't seem to be happening.
Personally I prefer the new behaviour.
But eitherways: it’s just an option.
I’m optimistic that they will eventually course correct on Liquid Glass, but we’ll have to wait until iOS/macOS 27, or perhaps longer.
There are parallels to Apple’s butterfly keyboard fiasco on the hardware side. Sleek looking on the surface but an objective step backwards in usability. Unfortunately it took Apple several years to reverse course on that one.
There are also parallels with the original pinstripes-and-transparency-everywhere aqua UI. I am also optimistic that it will be toned down over time but retaining the responsiveness.
The SD card slot on macbooks … not to mention the HDMI slot.
Here’s hoping that the glass effect goes the same way as the Dodo.
Hopefully iOS 26.x releases will continue to correct Liquid Glass, but I'm guessing iOS 27 is well down the path with it still integrated. Maybe iOS 28 will see sanity return???
It was not an entirely bad concept for the device it was conceived for, but Apple has a habit of unifying their technologies to all their products and sometimes, like with Liquid Glass, that seriously doesn’t work.
It started to break in 3 months, had unusable keys in 6...
Stop defending that idiocy.
I mean, "computing power" in a literal sense maybe, but does that matter if it doesn't translate to either "workload contention" or "electrical power"?
I think the Liquid Glass effects, similar to smooth scrolling, are mostly just running as pixel shaders on a spare tile of one of the SoC's GPU's Streaming Processors — a tile that likely likely would have been idle-but-burning-power-anyway, given that GPU power management occurs on the level of entire SPs. It's the same reason that ProMotion "smooth viewport scrolling" doesn't really cost anything.
Animating the Liquid Glass widgets (i.e. changing their position or shape), on the other hand, does seem to cost a lot / produce lag.
I get the impression that this is down to the UI toolkit not being optimized for whatever Liquid Glass is doing in terms of recalculating constraints during animations. (When the GPU overruns its time budget while computing shaders for the compositor, the visual effect is of [double-buffered] texture buffers dropping/repeating frames, not slowdown. Actual "lag" in a GPU-composited UI is either from CPU work, or from one-shot CUDA-type GPU "prerender jobs".)
I get the sense that Apple rushed out some shitty code that has some of these components re-evaluating a bunch of their placement and sizing constraints on every non-static animation frame (rather than just giving the Liquid Glass shaders the ability to do declarative tweens.)
Or maybe the shaders already do declarative tweens, but Apple are doing tons of redundant on-CPU per-frame recalculations, to re-do any constraint-based layout for everything around the component during the animation, that might be impacted by the component's current tweened state. I dunno.
Either way, it's definitely silly, and could be re-engineered to work a lot better.
But it's also not really "Liquid Glass's fault" (i.e. something inherent to the visual design); it's just (AFAICT) bad implementation engineering, rushed to give Apple something to talk about besides its failure to launch Apple Intelligence.
You can report an issue by typing applefeedback:// into Safari if you want.
Sounds like you need to spend some money for a new Apple device! /s
Just in one example video ( https://www.youtube.com/watch?v=0eCUkYJ8A98 ) they see the phone get hotter and the battery drops 13x faster during non-static sequences like checking notifications, etc.
Just anecdotally, my iPhone 16 Pro seems to last half as long. Before iOS 16, I got from 80% to 20% without a problem. Now, I charge to 100% and I still need to recharge throughout the day. Apple simply fucked up our phones.
Very consumer-hostile behavior from Apple :(
FWIW I’m sticking with the less secure one that doesn’t look like Windows Vista.
They are explicitly choosing to only release security updates for 18.x to devices which are not eligible for liquid glass.
iPhone 14 was deemed capable of running liquid glass, even though it has worse battery life and performs sluggishly.
In the past, Apple has usually let you hold back on an older version and shipped security updates for all devices, not just ones that are incapable of running the new OS, but not this time.
No they haven't been, for the past several years: https://www.macrumors.com/2025/12/19/ios-18-forced-ios-26-up...
Really wish Apple would get their software quality up from the gutter.
[1] https://www.macrumors.com/2025/12/18/macos-tahoe-studio-disp...
The flickering was so bad in my case that the pixels got stuck for some minutes when it happened.
But it's especially obvious when it dims itself based on ambient room brightness, I can actually see the vertical refresh happening as I move from a fully bright room to a dim one.
When I connect my laptop to a projector, I can select an individual window, or at least I used to be able to select a window and just project that. However, now when I try to select the window, as soon as the mouse cursor gets near the selection button, the button disappears!!! It has been driving me absolutely insane.
Weird green tints for no reason.. bubbles that take so long to inflate, you think your tap was dropped. Round edges that no longer fit the text content. Stupid ellipses at the edges of wrapped text. And all the functions that now take two taps when one used to do it. Text rendered on top of text for crying out loud! Whole view panes clobberin* each other. WebKit is a mess of wasted black bars where menus were hidden. Multiple flashes of white and black between content changes. It hits Apple apps as well as trashing third party layout.
Too many defects to list.
Headline: Apple celebrates 50th anniversary by burning down 40 years of human interface knowledge.
https://daringfireball.net/2025/11/software_update_tahoe_con...
I suppose it’s not really working, or is the product of a team and no other internal team actually use it.
Basically, the amount of stuff Apple can realistically change on the fly without restiching an entirely new system volume snapshot into place is quite small, so unless the stars align it can't be used.
[0]: https://security.apple.com/blog/memory-integrity-enforcement...
Relatedly, did Apple baseband have similar vulnerabilities as Broadcom WiFi/Bluetooth baseband?
Seriously, how hard is it to correctly measure the keyboard height and not render important UI elements, such as submit buttons, underneath it so you can’t click “Send”? It's getting close to unusable.
Update: No they haven't
If I want to fix it on my iPhone 16 I'm forced to update to iOS 26.
#!/bin/bash launchctl setenv CHROME_HEADLESS 1 defaults write -g NSAutoFillHeuristicControllerEnabled -bool false
It removes the drop-shadow from Chrome and removes an autofill context.
#!/bin/bash launchctl setenv CHROME_HEADLESS 1
defaults write -g NSAutoFillHeuristicControllerEnabled -bool false
I feel I should be at least given the security patches if I don’t want to update to Apple’s widely derided iOS 26 UI awfulness.
I have called and opened tickets, and I keep hearing it'll be fixed real soon now.
I ended up having to "delete messages from icloud" on all devices, escalate to support after they weren't deleted 45 days later (the UI shows -15 days in that scenario), reenable sync and then see it still failing to complete a Sync Now, redisable sync and re-delete messages in cloud, wait another 45 days, and then ask them to escalate to the iCloud backend team to run a purge on their end of just my messages in icloud records. It worked, but I don't know if they've had enough time for whatever corruption they found to be patched into their automated ops-repair/cleanup processes (and they wouldn't tell me if I asked), it's only been a couple months.
Your message implied a known issues with Messages affecting everyone. But that is not the case.