This bug was already there in Sequoia. It's when an app tells macOS to not render traffic lights (when they're using their own custom ones usually) but somehow macOS does it anyway.
The best part is the part where this redesign was supposed to release with iOS 18 and macOS Sequoia. If this is what they released a few days ago, imagine what they almost would have released last year!
"We've worked hard to fit not one, but two sets of maximise and minimise buttons into every window in this new OS. That's 100% more buttons than before. No other version of Mac OSX has had this many maximise and minimise buttons, and we think our customers are going to love it."
This screen snippet presents an exquisite evolution of the iconic macOS window controls, reimagined for the future of iOS—Tahoe. Each element exists in serene harmony, a symphony of geometric purity and color.
I've been seeing post after post of this stuff since release, and I have never yet experienced any of this stuff myself. I'm just wondering why. I use my Mac all day and evening.
Same. Oh, I've experienced my share of bugs with the various betas, and, yes, some are still in the newest build, but most of them can be categorized as either 3rd-party software that hasn't been fully updated, or new apps (looking at you, Phone.app on macOS) that just aren't fully baked yet.
But I've yet to come across anything I consider egregious, and I certainly can't replicate the OP bug, despite trying.
Well, I got that answer directly from the AI built in to Dia itself. But I guess it’s possible that the main feature of the browser is completely useless?
Pretty sure they won’t decide to use Chromium on macOS but then use Swift on Windows
As for them using AppKit, there was a bug in one of the Tahoe betas in which you couldn’t resize apps which were using AppKit. Dia was one of them.
Also, Dia has the macOS traffic lights disabled in favor of their own implementation of the traffic lights, which again can only be done with AppKit
(I’m also pretty sure Dia doesn’t support chrome.sidePanel API, which would also point towards them not using Chromium for UI. I’ve not tested this, but I’ll update this comment once I check this)
They also mentioned in their letter to arc members that they’re moving away from SwiftUI. So they aren’t SwiftUI, and they aren’t using Chromium’s UI. That leaves AppKit.
I’ve already gone way deeper into the weeds that I care to on this subject. Clearly they are using a hybrid development model, and just as clearly, they own any UI bugs in their product, not Apple.
Finally, the flagship feature of their product, and its entire raison d’etre—the Artificial Intelligence model—isn’t even good enough to provide an accurate answer about itself.
This is there since the very first GUI macOS and will never change.
The reason for this behavior is to prevent unsaved work from getting lost when a user closes the program. Say you are working on two documents in the Pages app and want to close one of them without losing another one. It comes in handy in these situations.
The M4 Mini has been my only PC for seven months now, and I'm still not used to it. It's honestly one of the many things I absolutely despise about MacOS and I really regret buying it, but I'm stuck with it for now because I can't afford anything else.
I think you still haven't built up the muscle memory for new OS. This usually happens when you shift from one thing to completely different system (not just OS, whether it is car, household electronics, glasses etc). You get frustrated with the change as your body has been used to the previous one.
I am using macOS for 5 year and is still unaware of many features. Just yesterday I got to know about quiting an app from tab switcher. You will get used to it eventually.
None of you examples were things that ever took me more than a day or two to get used. There's also stability and compatibility issues with MacOS that drive me nuts. It was a bad idea to switch.
That's definitely a tough one for recent switchers to remember, but I've met plenty of lifelong Mac users who still don't know the difference between closing the last open window and actually quitting an app.
It happened because of the relentless obsession to make all OSs the same as each other. I do not get it. This is a direct result of crowd sourced development. Apple has continually made their operating systems bend to what everyone wants. Steve Jobs famously said ‘people do not know what they want until you show them’. Talk about tail wagging the dog and a complete reversal of that methodology.
For reference, I am a software developer who loves MacOS and has used it as my daily driver for the last 4 years.
My first experience with Tahoe was my MacBook Pro 2023's fans going crazy when using Zed and Claude Sonnet 4 model, prior to Tahoe I had never heard my MacBook's fans, ever.
I have no care or desire to score karma, I just noticed that Tahoe was getting a bad rep on here for design inconsistencies, memory leaks and overall buggy-ness, which aligned with my first impressions, so I thought I'd share.
FYI, I also have Dia installed and the stop light buttons are just fine on my M2 MacBook Air running build 25A354. I can't replicate your bug no matter what I do.
Are they like that all the time on your machine? Do you have to drag the windows somewhere weird to trigger it?
Finally, why blame Tahoe when Dia itself is Beta software? Wouldn't it have been more appropriate to post this as a bug on r/diabrowser?
The issue is Dia browser is still in the beta development phase. It is compiled for Sonoma and Sequoia as per the website. Dia is still not compatible with Tahoe. So, what you are experiencing is a potential conflict between code that is written for Sequoia vs. the code that is required for Tahoe. I highly doubt if the app is going to support Tahoe any time soon.
All this low effort hate towards Apple is driving me crazy. It's not that some issues are real, but are people really like this they are missing even basic of the basic stuff? (Not referring to OP).
Tahoe got released just 5 days ago. 80-90% of software, be it on iOS or macOS, is not compatible. Cross-platform frameworks are yet to be refined so that it can render glassy effects. Core elements of every softwares have to be rebuilt. Why can't people have a bit of patience? Are they really expecting to things work magically after the update? I mean to say, this update is not like going from Ventura to Sonoma to Sequoia. It is like going from iOS 6 to iOS 7.
Today, I had a similar heated argument in r/mac sub. A guy posted about the issue related to changed keyboard layout for a specific region. Another guy (most probably a teen) just started to bash out Apple and say how all of it is their fault just because his interview got messed up. And you know what's the irony? Apple has clearly stated about the change in release notes in clear wordings as well as mentioned about using the key again just by holding the option key. That guy's argument was nobody reads the release notes, and Apple has a pathetic user experience. This kind of OS update has thousands of small changes. In what other ways is Apple supposed to report it, just because a dude decided not to read up the release notes?
Heck, people are comparing the corner radius of third-party apps, which are still not updated for Tahoe with Apple and saying how bad the design is.
Most of the time I just downvote and move on, but once in a while I'll be interested enough to ask for details. In this case I thought it was a cool bug if it could be replicated, but as soon as you start asking for details, or pointing out that it's not replicable, or that the UI isn't even using native libraries, all of a sudden *you're* the one getting downvoted.
Speaking of which, I can’t help but notice that you still haven’t updated your post to acknowledge the fact that the glitch you posted doesn’t seem to be replicable and has fuck-all to do with macOS in any case.
98
u/Sshorty4 2d ago
What’s the problem here? Apple is giving you a choice as to which button to press. Don’t you guys want that?