I've noticed lately, on multiple platforms, that after an update, a reboot (even if, theoretically, it's already done automatically) tends to fix several minor issues.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Tahoe 26.3 RC - Bug fixes, changes, and more
- Thread starter WilliApple
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Especially first reboot after system is updated. Was already getting ready to do safe boot, clearing caches and many more things but for now that one reboot solved it.
One major observation is that graphic performance issues with Orion browser seem to be finally resolved. It was horrible on 26.1 and 26.2.
One major observation is that graphic performance issues with Orion browser seem to be finally resolved. It was horrible on 26.1 and 26.2.
tkermit
macrumors 68040
fisherking
macrumors G5
good catch! will add that to my feedback assistant report now...
According to release notes, the window resize issue that people have been reporting all over the Internet has been fixed.
Also this should be a pretty huge indication that, even though there is likely to be design changes in OS 27, the rounded windows are going absolutely nowhere.
So might as well get used to them because they will likely be staying around a while. Like, 10 years a while.
“AppKit
Resolved Issues
- Window resize areas now follow corner radius instead of using square regions. (149726089)”
Also this should be a pretty huge indication that, even though there is likely to be design changes in OS 27, the rounded windows are going absolutely nowhere.
So might as well get used to them because they will likely be staying around a while. Like, 10 years a while.
It looks like when resizing handle area bug was fixed, QuickLook window resizing functionality got lost. Fixing one problem introduced new one.
fisherking
macrumors G5
fisherking
macrumors G5
huh? are you talking about resizing quicklook windows? (am having this issue with stickies as well). can't tell if you're: serious, making a joke, thinking it's a good thing, or?? anyway, hope it's fixed soon...
I'm not joking and I absolutely hope that this would be fixed, but there's really no way to know.
Tahoe introduced another bug in QuickLook framework as well (markups are misplaced if image is resized before adding markup and saving it). That bug is still not fixed while I have reported it long time ago. There is a way to just tell users to "p... off" and learn to live with new behavior what comes to resizing (new post-Monterey Systen Settings window can be resized only vertically), but not with an obvious problem with markup - but still QuickLook markup is not fixed and there's no way fot it to be "intended behavior".
If Apple was able to get away with Liquid Glass madness then declaring inability of resizing QuickLook windows as "intended behavior" is peanuts compared to that. I just mean that they actually can be that mad if they want to.
Don't forget that in Snow Leopard times any window could be resized from only one corner..
Tahoe introduced another bug in QuickLook framework as well (markups are misplaced if image is resized before adding markup and saving it). That bug is still not fixed while I have reported it long time ago. There is a way to just tell users to "p... off" and learn to live with new behavior what comes to resizing (new post-Monterey Systen Settings window can be resized only vertically), but not with an obvious problem with markup - but still QuickLook markup is not fixed and there's no way fot it to be "intended behavior".
If Apple was able to get away with Liquid Glass madness then declaring inability of resizing QuickLook windows as "intended behavior" is peanuts compared to that. I just mean that they actually can be that mad if they want to.
Don't forget that in Snow Leopard times any window could be resized from only one corner..
Last edited:
tkermit
macrumors 68040
Apple is on it, apparently: https://developer.apple.com/forums/thread/814798.
Let's see whether we get another RC tonight
There are 3 options:
- 25D122 will be made RTM and this will be fixed in 26.3.1, later or not at all
- There will be next build which will be RTM
- There will be RC2
Last edited:
I suppose, once again, it depends on how long they need to supply it with the new M5 Macs rather than on quality control.
SDAVE
macrumors 601
Still crazy to me that a beta has such big impact on simple tasks. Do they intentionally bork things as they continue to clean up the code? Really unprofessional behavior
fisherking
macrumors G5
it's a beta (as you've pointed out), and, in the process of inventing/reworking/upgrading things, some things get fixed, and some get borked. if you want a more professional experience (well, hopefully), stay off of the betas. 🤔
SDAVE
macrumors 601
It's technically RC. It's a 4 trillion dollar company I assume they can shift funds and make their team that handles updates better.
Imagine if an update for Windows comes out and you can't resize a simple window in finder.
fisherking
macrumors G5
imagine if apple could envision every last issue that might pop up for every one of it's estimated over-100 million users.
more importantly; new OSes are invention, built upon previous tech, with new code, new ideas... and (as history shows us), it's always a work-in-progress. it will never be perfect (but hopefully they'll always be striving for that).
SDAVE
macrumors 601
Lol the Apple apologists never cease to amaze me.
It's an iteration not an invention.
There aren't major updates in Tahoe except the GUI and some under the hood updates and systemwide apps/features that tie into the iOS ecosystem. This is also apparent in every yearly macOS update.
Every .0 macOS update is very buggy, but its hilarious that Apple still hasn't gotten their stuff together to make it not so buggy.
fisherking
macrumors G5
i agree (about the apple apologists). meanwhile...
all software is invention; it's a moving-forward into uncharted territory, built on the foundation of what proceeded it. so that's any OS, any app. it's not as simple as 'make it less buggy'... because:
a. it's new, and untested (that's what we're supposed to help with, as beta users... those who are on the betas).
b. there's no way to anticipate every user experience; there are too many people with too many variables.
c. OSes keep getting updates, until, finally, there's a new OS (and even then, sometimes a previous OS gets an update)... because there's no final point, when everything is perfect.
software is a never-ending story, there's no final page.
SDAVE
macrumors 601
PotentPeas
macrumors 6502a
Yeah ... this isn't a thing that happens sometimes, to some people. This is an issue on a core windowing function that can seemingly be reproduced on anyone's system. The fact that this came out to the public at all is a QC failure. They should, at a minimum, have automated tests checking basic functionality of their window controls (among other various functions of the OS) that run after each build. Automated testing is a core part of software development (especially for companies with a budget like Apple's), and if they are slacking on it then they are *asking* for trouble like this. (To note, I am a software developer, and this has been beaten into me from my earliest days.)
If they knew that there was such an issue and pushed it out in a beta anyway, with the intent to fix it later... maybe. But pushing an RC says "we intend to release this", so it shouldn't have any major known issues. Which just says that Apple isn't treating the "RC" term properly, or they truly didn't know about this, which is a testing failure. (Seems like the latter based on the feedback on the developer forum.)
If they knew that there was such an issue and pushed it out in a beta anyway, with the intent to fix it later... maybe. But pushing an RC says "we intend to release this", so it shouldn't have any major known issues. Which just says that Apple isn't treating the "RC" term properly, or they truly didn't know about this, which is a testing failure. (Seems like the latter based on the feedback on the developer forum.)
Last edited:
SDAVE
macrumors 601
This is one of many I've seen with Tahoe. It's clearly the worst release in recent macOS history.
They borked Electron apps system wide and had to release a patch...etc.etc
Tahoe feels like a vibe coded release...it's hilarious for a 4 trillion dollar company.
Now it looks like this problem tries to resurface from time to time. One other remediation seems to be force-quitting System Settings.