My workaround for this issue is to put Mail app in its own dedicated Space/Desktop. Then it only comes to the front in its own Space, not in the Space I'm normally using.
I've switched back to a new MacBook, temporarily due to COVID as it was easy to purchase from Apple and it was an emergency.
I used OS X fulltime 2006-11. I'm surprised how buggy Catalina is, including Mail.app. I have had serious firmware issues too, such as needing to reset my SMC very frequently because my USB C stops charging the machine every other day. Apple is clearly, sadly, neglecting mac OS.
Surprisingly, I haven't disliked butterfly keys as much as I thought I would do. I can type extremely fast. I do prefer their scissor keys, though, which are really good and low latency [1].
Yes, it's new and it's fairly decent. I love mechanical keyboards (especially those with ALPS and TOPRE switches), but I realize low travel means I type much faster and it doesn't tire my fingers.
IMHO the scissor keys in the Magic Keyboard are really good because they strike a perfect compromise in terms of depth, comfort and speed. Also the board is really low latency. Not sure what tricks Apple has played with the firmware in those keyboards.
I get something like this with Music.app -- it seems to randomly open. I suspect it's some kind of keystroke (i.e. hitting the play button) but I haven't figured out exactly why it's happening or how to stop it.
I'm pretty sure this didn't used to happen until I upgraded to Catalina.
I get this semi-randomly when I'm using my bluetooth headphones/mic with Meet/Discord and then quit/close it and it becomes available to the OS or something. Music.app just pops up and as far as I can tell, there's no way to turn it off.
Apple definitely has a history of not acknowledging for a long time major problems that many people can clearly demonstrate. Bend gate, antenna gate, stage light gate, that thing with the coating on the screens...
The screen coating is still an issue. It crops up again every few years. I’ve gotten a few macs replaced for free because of it even when I didn’t mind.
> Bend date, antenna gate were fixed in the next revision of their hardware.
I know they were. But do you not remember there was quite a period of time where Apple didn't acknowledge the problems and ignored users trying to triage them?
> There is a limit to how quickly Apple can fix
What has this got to do with it? We're talking about triage and acknowledgement, not fix.
Flexgate is still a real, profound, and disgraceful defect.
This is the one where your MacBook Pro’s screen stops working because Apple ran a ribbon cable through a hinge or some such stupid shit. Been happening since 2016 and still rendering $4000 laptops useless after 18 months of light use.
> I can assure that when I was working at Apple bugs were triaged and acknowledged
As a counterexample, as late as 2018 Apple was publicly denying (so not acknowledging and ignoring attempts at triage) bendgate, but leaked documents show they knew about it in 2014.
"Doesn’t mean they get fixed though."
Ok then! I am driven to report it now!
Actually, this is a trouble bugs lots and lots of people for long long time. I browsed countless articles or threads about this with tons of workarounds. Where more than a few are Apple discussions. If it is not reported yet - from outside or inside - then it does not exist. But it does.
Radar’s asinine search functionality also obscures the seriousness of bugs by failing to reveal dupes.
It doesn’t (or at least didn’t) default to searching for all words used in the title; it only searches for the EXACT string you enter. It was a pain in the ass to even find bugs YOU wrote.
I couldn’t believe how goddamned dumb this is, or the Radar team’s response: Oh, you simply use Oracle syntax and wildcards in the title search! No explanation of how we were supposed to know this, or WHY.
They take forever to answer, and ask for things that you have already provided in your original issue. When you try to reproduce the bug on multiple versions, they close your bug if you reproduced it on beta versions, because beta versions are unsupported, even though the bug affects release versions. Sometimes this happens even if they asked you to try the beta version!
The bugs are almost always closed as duplicate of another bug, which, of course, you can't see because the bug tracker is private.
The bugs are never fixed, at least no bug that I have ever reported has been fixed. Years or months later after submitting a bug that happens not to be closed as duplicate of another bug, they get closed because a new version of macOS is released, and you are encouraged to resubmit your report if it still affects the new version, which inevitably it does...
Even if the bug is in some open source component, and you provide a patch, it is ignored and eventually closed as explained above.
It's a total waste of time and a pain in the ass to submit bugs to Apple.
You can’t see other people’s bug reports because they often contain screenshots or telemetry data which is confidential.
And I believe the way Apple works is to look through Radar for important/widespread bugs, mark them for fixing in the next release, fix them and then ask you to retest. They aren’t just going through and fixing Radar’s one by one. Hence you get that frustrating experience where it looks like the bug is being ignored.
I wish that was how it worked, but my experience has been more like the parent poster's: long-standing easily reproducible bugs never fixed despite multiple reports and multiple major releases. I've never once been informed by Apple of a bug I submitted being fixed, or "asked to retest".
Not being able to see the duplicate bug when your case is closed and marked as such feels like a slap in the face. I understand that some material could be confidential, but I would bet over 99% aren't. If someone has spent enough time to determine that my report X is a duplicate of Y, they could also determine if Y is confidential and if so, just flag it in the system to show up as redacted.
> You can’t see other people’s bug reports because they often contain screenshots or telemetry data which is confidential.
You know what would be great? If I could mark my bug as “please let everyone be able to find this”. But Apple refusing to add this feature shoes that they still do not fundamentally understand and/or care about how external feedback works.
I usually file bug reports but this issue was already well documented in their support forum even by official Apple staff so I'd assume they would at least file the issues if they see something show up there?
I’ve had this issue for a long time now across a couple of versions of MacOS and three Macs. It appears to be related to Google Calendar. My current workaround is to hide a Mail window with CMD-h. I’ve given up trying to report it or find a fix.
Can confirm, same here. As long as you hide the window (cmd-h) instead of closing it (cmd-w), the problem doesn't ever come up. I've been using this work-around for over a year now.
I second this. For me it seems to happen at very specific times, like 12AM so it leads me to believe it had to do with calendar events. And it always does it a few times in succession.
When I tried Airmail, they sent an email that had something like "oh, we see that you use @<domain>.com. Do you think you could reach to your colleagues and talk to them about using Airmail". I deleted the app immediately.
It still pops up when it's minimised. I blame this bug for my inboxes going to crap over the past year, because the only fix for me is keeping Mail closed and opening it only when I really need to.
Apple Mail is riddled with bugs it’s unusable. Do yourself a favor and switch. Anything else is better than it, Thunderbird is a pretty good alternative imo.
It feels like apple doesn’t put any care into regression bugs in their applications. It’s the same on the iPhone, Mail is so bad that I uninstalled it in favor of outlook (the irony...) —Mail was sucking so much battery that my phone wouldn’t last 8h. With outlook it lasts all day (12+h)
What configuration are you running? This bug happens to me several times a day, though I am trying to close Apple Mail when I am not using it, but that's easy to forget and also annoying.
Same. The only issue I have noticed is that Mail sometimes freaks out when I lose internet connection. It’s pretty rare for that to happen and it doesn’t freak out every time, either. I have not experienced any of the bugs other people are having.
I have six different email accounts with a ton of folders.
I have been using Mail for many years. Like OP, I have Gmail on own domain (in my case it’s the old personal G Suite offering). Additionally, I have a regular Gmail account and iCloud’s built-in email. Like OP, I did a clean install when Catalina came out (got a new laptop around that time).
As far as I’m concerned, Mail is one of those things that consistently just works. The only issue I used to have was quirky undo/redo of archivals/deletions, which I believe had to do with Gmail’s IMAP servers and/or the way Mail talks to them, but I am not noticing that lately.
If I were OP, I’d consider again whether third-party software that they and their coworkers have in common is wreaking havoc here. If there’s no such software or the issue manifests itself on a clean system without any third-party apps at all, then this Heisenbug should probably on Apple’s Radar…
The best thing about Apple Mail is their integration with contacts and everything "i" Phone, Pad, etc.
It is the whole ecosystem lock down deal again. Nothing has progressed in tech in this aspect, each company is still for themselves instead of consumers.
I have 16 GSuite accounts setup and have never had this issue in Mail. Even if my account login fails or the server is unreachable, the app does not automatically come to the foreground. I don't use full screen or spaces though (I prefer Moom) so maybe that's why I have never seen the issue.
I’ve been using Apple Mail on both desktop and iPhone for many years. It’s not perfect, but I’ve found it far superior to the alternatives, including Thunderbird and Outlook.
Some bugs like this are terrible as I’ve hit the screen split bug several times. But Apple Mail has features like all messages in a single window including replies that don’t exist elsewhere. It’s also fast and smooth mostly with conversations being just right. Thunderbird is mostly OK but is a clunker for these particular areas, imo.
This has been annoying me for months. It’s particularly irritating when you’re screen sharing. I just make sure Mail is quit when I’m not using it, which isn’t ideal.
I have the same issue, in fact I'm so used to it that I even do not notice it anymore, except when watching fullscreen video, then I'm like: "It's just the way how things are here...[quits Mail]".
As someone already mentioned - I'm also pretty sure it's related to some disconnect/reconnect thing.
There's no reason why it shouldn't affect all google mail accounts equally. If the cause is frontend disconnections, it will happen to any account tier.
How is it that there is still no known root cause for this issue? I suspect there is a way to check what the reason an app came to the foreground is, no?
The reason is that Mail thinks the mail server is unreachable, so it brings the window to front, but then magically it changes idea and the mail server is reachable again ️.
Could be worse! Outlook on Windows just locks up entirely while it tries to connect. I don’t know why they’re still doing network IO in the UI thread - over 10 years after they admitted it was a major problem.
In general I find macOS handles alerting the user very poorly.
I don't know why but it infuriates me when icons bounce on the dock for attention. The animation is too insistent for whatever trivial thing the app wants to let me know.
Or an app will open some Important Dialog Box that I need to deal with, except it's hidden behind some other windows somewhere and the rest of the app refuses to respond to my clicks until I find the dialog box. It doesn't bother foregrounding the dialog box for me.
Yeah, that's not good. Sometimes you can find it through some combination of ensuring that app is frontmost by clicking its icon in the dock, choosing "hide others" from its menu, and triggering "show application windows" in Mission Control (often ctrl-down-arrow, or a three-finger down-swipe trackpad gesture).
Due to the explosion in videoconferencing I've spent some time recently helping family set things up via remote desktop (I highly recommend Chrome Remote Desktop by the way, pretty easy to set up). This kind of thing is absolutely inscrutable to non-tech savvy people. All they see is that the computer suddenly stops doing anything but playing an annoying "donk" sound whenever they click and they have no idea that any of those features exist.
Really, Windows with its `window == app == taskbar item` approach is far easier to understand.
I’m still on High Sierra (10.13) and this happened to me only three hours ago installing QCAD.
I switched out to another program for a moment during installation and when I switched back a QCAD installation dialogue box was hidden by the main QCAD installation window.
I was able to drag the obscuring window out of the way, but still seems daft not to focus on the interaction blocking window.
> I don't know why but it infuriates me when icons bounce on the dock for attention. The animation is too insistent for whatever trivial thing the app wants to let me know.
The animation is fine, it’s just that bad app developers abuse it for the most trivial things. I’m looking at you, Music.app and Microsoft AutoUpdate.app. (“You’re playing music elsewhere” for the former, which I am not but thanks for suggesting I’m trying to be a pirate; “I finished one part of a multi-part update and automatically continued” for the latter.)
I hint that the root cause is a stupid design decision. Forcing the app into the front, for whatever reason. Without the means to turn the behaviour off.
I experience this as well after upgrading to Catalina. I thought it was my fault at first, caused by some sort of key combo. It only happens for me when in full screen with another app.
I am still not on Catalina yet and it started for me ca. 6-9 months ago. Perhaps with some Mojave update.
(unsure as no big changes occurred and it took some time to see being a systematic trouble)
I am more and more turning off system updates (not only Mac) as those bring more trouble than good. Being a very late adopter pays off.
(update to Catalina is still not in the middle term plans)
hits me too and it‘s really annoying... I even got used to quit Mail.app but yeah... it‘s bad.
My feeling though is that google is more and more saying goodbye to standards... just a feeling
It is not a bug, it is a feature.
Someone out there had to write the code that pushes the mail app to the front. It does not happen spontaneously, someone made it happen. And made it an exclusive behavior without user control.
It must have been a conscious feature.
A mindless and stupid one, but still a feature.
No bug to fix here.
(after suffering and spending toooo much time of experimenting I decided to get rid of the Google account approach of the Mac but use it as an IMAP account, turning off 'safe' access in my Google account)
> Someone out there had to write the code that pushes the mail app to the front.
Sometimes the code you write doesn't do what you had in mind. Or worse: gets triggered by side effects of something unrelated.
I don't think it's intentional in this case but even if it would be intentional after seeing this many bug reports everywhere you'd have to reconsider and make connection errors less intrusive.
You do not push the whole app to the front by mistake, especially at some glitch of connection as it is happening here!
It is not a typo or whatever kind of mistake just happens on its own but had to be a conscious action!!
I write code, I make mistake, but this is beyond that!
It is also neglected for years now while being very widespread, no way of being unnoticed and left there if it wasn't a conscious choice to do so!
I don't have any issues with Apple Mail but I do have issues with zoom, randomly switching from full screen sharing to the desktop and back again, it's incredibly annoying. It doesn't happen when I share my screen, only when others do. It seems to have gotten better recently but still happens in occasion. Anyone else seeing this? Maybe it's related?
I have another zoom problem on Mojave. Even though I marked the zoom windows to use Desktop 2, they keep opening on Desktop 1 :-/ any tips on how to fix this?
I've had this issue for the past 2–3 years. It seems to happen because of improper error handling. If you look closely at the app in the instant it opens, your affected account will have a “disconnected” symbol next to it in the sidebar. However, it goes away before an error can be shown.
My theory is: there is a momentary connection issue with these G Suite accounts, and Mail.app starts to show an error by focusing itself, but the error is resolved so quickly it doesn't actually get to show the “connection problems” modal.
I hope this can be fixed soon, it's been a daily annoyance for me for a long time now.
Yet, to force an app to the front when glitch in connection happens is more like a feature they deliriously thought is being useful, instead of choosing other means of notifications, which is plenty.
An app is not forcing itself to the front without someone is specifically writing the code for it to do.
Exactly. I found the bouncing animation genius, as it always reminded me of a toddler impatiently jumping up and down for attention. Doesn't mail.app do this?
Mail.app and most other apps since 10.8 (?) introduced badges just use those, unless it’s a more urgent thing than “you have a new message” in which case, yes, it will bounce the dock icon.
I wrote a SIMBL plugin at one point to neuter applications that did this too much (actually, I forked it from someone who wrote it for Spotify). Trying to grab my attention in a persistent, repetitive way for something that is minor drives me up the wall.
I vaguely remember it having history, but the native system does have something similar in that panel you get by swiping with two fingers from the right edge of the trackpad, in "notifications" tab.
The author's assessment is incorrect btw, this happened to me frequently for years on a computer without any G suite accounts. On a High Sierra machine fwiw.
Solidly on Linux Mint now but back in the day when wrangling MacOS I used Hammerspoon to fix these sort of issues - should be doable to monitor and enforce the background status of Mail.app and then pause the monitoring when invoked by user (easiest thing would likely be to set hotkey that then also pauses monitoring), and finally resume monitoring when Mail.app goes to background (i.e. user done with active interaction).
In my experience, if you always hide the Mail window (cmd-h) instead of closing it (cmd-w), it won't ever pop back up. Takes a while to retrain the muscle memory though!
I haven't tested this in Catalina, but it definitely works consistently in Mojave.
Mind you, a program with “hidden” windows open takes up more CPU/memory than a program without any windows open, because the view-controllers for those windows are still running, just bound to an invisible, non-updating view. (Though, admittedly, it’s less of a CPU cost than minimizing the window, since that requires the view to be kept active too, to facilitate updating the live thumbnail.)
The main place this comes up is in cases where the main window is doing something clever to gather the information to display itself. For example, Activity Monitor doesn’t suddenly stop using half your CPU when you hide it.
Mail.app probably keeps a big scrollable list-control for the selected view in-memory for as long as you have the window open. So it might be a bad idea to do this if you’re one of those people who never archive anything (i.e. practice “Inbox Infinity.”)
> Though, admittedly, it’s less of a CPU cost than minimizing the window, since that requires the view to be kept active too, to facilitate updating the live thumbnail.
I thought that was a static thumbnail?
> For example, Activity Monitor doesn’t suddenly stop using half your CPU when you hide it.
It does for me, which is why I keep it hidden when I’m not actively using it.
Nah, it updates (...as far as I can recall.) Try opening a chat client, minimizing the chat window, and then sending a message from another device to yourself.
I believe it’s just using the same call into the compositor that Mission Control uses to display your windows and spaces. Those are all live. (They might have a lower update rate, though.)
> It does for me, which is why I keep it hidden when I’m not actively using it.
Interesting. This might be down to Activity Monitor being written to respond to a message letting it know that its view is entirely obscured, and the Activity Monitor main-window view-controller deciding in response that there’s no point in it polling the system if all it’s going to do when re-visible is discard all the stuff it learned in the mean time and re-poll again to get the newest data for the view.
I can’t recall whether Activity Monitor has any historical/time-series views built in? If it does, then if you hide Activity Monitor with those active, it should keep using CPU, to gather the data for that view, whether it’s rendering it or not.
> Mind you, a program with “hidden” windows open takes up more CPU/memory than a program without any windows open
I can’t speak to Mail, but in general a Mac app with no visible windows may actually take zero CPU, because (if it’s written to allow for it) the OS may kill the process entirely.
This issue has been a real nuisance for at least 5 years and I could never retrain myself. One solution that worked for me was to make it full screen with its own Space.
177 comments
[ 4.6 ms ] story [ 118 ms ] threadI used OS X fulltime 2006-11. I'm surprised how buggy Catalina is, including Mail.app. I have had serious firmware issues too, such as needing to reset my SMC very frequently because my USB C stops charging the machine every other day. Apple is clearly, sadly, neglecting mac OS.
Surprisingly, I haven't disliked butterfly keys as much as I thought I would do. I can type extremely fast. I do prefer their scissor keys, though, which are really good and low latency [1].
[1] https://danluu.com/keyboard-latency/
IMHO the scissor keys in the Magic Keyboard are really good because they strike a perfect compromise in terms of depth, comfort and speed. Also the board is really low latency. Not sure what tricks Apple has played with the firmware in those keyboards.
I'm pretty sure this didn't used to happen until I upgraded to Catalina.
I really wish I had better luck with Linux...
launchctl unload -w /System/Library/LaunchAgents/com.apple.rcd.plist
(https://www.howtogeek.com/274345/stop-itunes-from-launching-...)
Your bug will at least then be triaged and acknowledged.
Lol sure it will.
There is a limit to how quickly Apple can fix hardware given they have to work with third parties on retooling and retraining.
I know they were. But do you not remember there was quite a period of time where Apple didn't acknowledge the problems and ignored users trying to triage them?
> There is a limit to how quickly Apple can fix
What has this got to do with it? We're talking about triage and acknowledgement, not fix.
This is the one where your MacBook Pro’s screen stops working because Apple ran a ribbon cable through a hinge or some such stupid shit. Been happening since 2016 and still rendering $4000 laptops useless after 18 months of light use.
And I can assure that when I was working at Apple bugs were triaged and acknowledged by a PM. Doesn’t mean they get fixed though.
As a counterexample, as late as 2018 Apple was publicly denying (so not acknowledging and ignoring attempts at triage) bendgate, but leaked documents show they knew about it in 2014.
https://www.slashgear.com/iphone-6-bendgate-docs-confirm-app...
> Doesn’t mean they get fixed though.
We're not talking about fixing - we're talking about triage and acknowledgement.
Actually, this is a trouble bugs lots and lots of people for long long time. I browsed countless articles or threads about this with tons of workarounds. Where more than a few are Apple discussions. If it is not reported yet - from outside or inside - then it does not exist. But it does.
It doesn’t (or at least didn’t) default to searching for all words used in the title; it only searches for the EXACT string you enter. It was a pain in the ass to even find bugs YOU wrote.
I couldn’t believe how goddamned dumb this is, or the Radar team’s response: Oh, you simply use Oracle syntax and wildcards in the title search! No explanation of how we were supposed to know this, or WHY.
TIL
It’s “Feedback Assistant” now and at least one level removed from Radar now. Can’t give third party developers a direct line to engineers!
> And I can assure that when I was working at Apple bugs were triaged and acknowledged by a PM.
They used to, maybe? Not anymore. I think I got two responses in June 2019 and then nobody has looked at my bugs since.
They take forever to answer, and ask for things that you have already provided in your original issue. When you try to reproduce the bug on multiple versions, they close your bug if you reproduced it on beta versions, because beta versions are unsupported, even though the bug affects release versions. Sometimes this happens even if they asked you to try the beta version!
The bugs are almost always closed as duplicate of another bug, which, of course, you can't see because the bug tracker is private.
The bugs are never fixed, at least no bug that I have ever reported has been fixed. Years or months later after submitting a bug that happens not to be closed as duplicate of another bug, they get closed because a new version of macOS is released, and you are encouraged to resubmit your report if it still affects the new version, which inevitably it does...
Even if the bug is in some open source component, and you provide a patch, it is ignored and eventually closed as explained above.
It's a total waste of time and a pain in the ass to submit bugs to Apple.
And I believe the way Apple works is to look through Radar for important/widespread bugs, mark them for fixing in the next release, fix them and then ask you to retest. They aren’t just going through and fixing Radar’s one by one. Hence you get that frustrating experience where it looks like the bug is being ignored.
You know what would be great? If I could mark my bug as “please let everyone be able to find this”. But Apple refusing to add this feature shoes that they still do not fundamentally understand and/or care about how external feedback works.
Also checked on https://openradar.appspot.com if there's anything but there wasn't.
Last time I tried it, it was vulnerable to a bunch of issues similar to XSS.
I suggest you test it with https://www.emailprivacytester.com/ and see if it still finds anything.
It feels like apple doesn’t put any care into regression bugs in their applications. It’s the same on the iPhone, Mail is so bad that I uninstalled it in favor of outlook (the irony...) —Mail was sucking so much battery that my phone wouldn’t last 8h. With outlook it lasts all day (12+h)
Weird, I've been using it for a decade and I have zero issues. Maybe 'unusable' is a pretty subjective assessment?
I have six different email accounts with a ton of folders.
As far as I’m concerned, Mail is one of those things that consistently just works. The only issue I used to have was quirky undo/redo of archivals/deletions, which I believe had to do with Gmail’s IMAP servers and/or the way Mail talks to them, but I am not noticing that lately.
If I were OP, I’d consider again whether third-party software that they and their coworkers have in common is wreaking havoc here. If there’s no such software or the issue manifests itself on a clean system without any third-party apps at all, then this Heisenbug should probably on Apple’s Radar…
It is the whole ecosystem lock down deal again. Nothing has progressed in tech in this aspect, each company is still for themselves instead of consumers.
I don't know if apple just decided to give up on it or what but it's got a lot of bugs that have been left for years.
Random crashes, sudden 100% CPU or memory usage... It sometimes just stops receiving mails altogether.
I can only use Outlook to work at work which is frustrating
As someone already mentioned - I'm also pretty sure it's related to some disconnect/reconnect thing.
I don't know why but it infuriates me when icons bounce on the dock for attention. The animation is too insistent for whatever trivial thing the app wants to let me know.
Or an app will open some Important Dialog Box that I need to deal with, except it's hidden behind some other windows somewhere and the rest of the app refuses to respond to my clicks until I find the dialog box. It doesn't bother foregrounding the dialog box for me.
Really, Windows with its `window == app == taskbar item` approach is far easier to understand.
I switched out to another program for a moment during installation and when I switched back a QCAD installation dialogue box was hidden by the main QCAD installation window.
I was able to drag the obscuring window out of the way, but still seems daft not to focus on the interaction blocking window.
The animation is fine, it’s just that bad app developers abuse it for the most trivial things. I’m looking at you, Music.app and Microsoft AutoUpdate.app. (“You’re playing music elsewhere” for the former, which I am not but thanks for suggesting I’m trying to be a pirate; “I finished one part of a multi-part update and automatically continued” for the latter.)
All in all, a bit buggy application it seems.
I use Mail with a GSuite account as well.
I am more and more turning off system updates (not only Mac) as those bring more trouble than good. Being a very late adopter pays off. (update to Catalina is still not in the middle term plans)
Admittedly I am not a developer, and none of the software I’ve wanted to run has required a more recent version.
(after suffering and spending toooo much time of experimenting I decided to get rid of the Google account approach of the Mac but use it as an IMAP account, turning off 'safe' access in my Google account)
Sometimes the code you write doesn't do what you had in mind. Or worse: gets triggered by side effects of something unrelated.
I don't think it's intentional in this case but even if it would be intentional after seeing this many bug reports everywhere you'd have to reconsider and make connection errors less intrusive.
My theory is: there is a momentary connection issue with these G Suite accounts, and Mail.app starts to show an error by focusing itself, but the error is resolved so quickly it doesn't actually get to show the “connection problems” modal.
I hope this can be fixed soon, it's been a daily annoyance for me for a long time now.
Yet, to force an app to the front when glitch in connection happens is more like a feature they deliriously thought is being useful, instead of choosing other means of notifications, which is plenty. An app is not forcing itself to the front without someone is specifically writing the code for it to do.
That's how apps "notified" back then.
Polite apps would just bounce their dock icon rather than stealing focus, however.
Mail.app and most other apps since 10.8 (?) introduced badges just use those, unless it’s a more urgent thing than “you have a new message” in which case, yes, it will bounce the dock icon.
[0] https://youtu.be/ks-N4rI_1RU
The author's assessment is incorrect btw, this happened to me frequently for years on a computer without any G suite accounts. On a High Sierra machine fwiw.
Now I'm running Mavericks and it never happens.
I find myself quitting mail when I want to be in the zone because otherwise this random behaviour is really annoying.
I haven't tested this in Catalina, but it definitely works consistently in Mojave.
The main place this comes up is in cases where the main window is doing something clever to gather the information to display itself. For example, Activity Monitor doesn’t suddenly stop using half your CPU when you hide it.
Mail.app probably keeps a big scrollable list-control for the selected view in-memory for as long as you have the window open. So it might be a bad idea to do this if you’re one of those people who never archive anything (i.e. practice “Inbox Infinity.”)
I thought that was a static thumbnail?
> For example, Activity Monitor doesn’t suddenly stop using half your CPU when you hide it.
It does for me, which is why I keep it hidden when I’m not actively using it.
Nah, it updates (...as far as I can recall.) Try opening a chat client, minimizing the chat window, and then sending a message from another device to yourself.
I believe it’s just using the same call into the compositor that Mission Control uses to display your windows and spaces. Those are all live. (They might have a lower update rate, though.)
> It does for me, which is why I keep it hidden when I’m not actively using it.
Interesting. This might be down to Activity Monitor being written to respond to a message letting it know that its view is entirely obscured, and the Activity Monitor main-window view-controller deciding in response that there’s no point in it polling the system if all it’s going to do when re-visible is discard all the stuff it learned in the mean time and re-poll again to get the newest data for the view.
I can’t recall whether Activity Monitor has any historical/time-series views built in? If it does, then if you hide Activity Monitor with those active, it should keep using CPU, to gather the data for that view, whether it’s rendering it or not.
I can’t speak to Mail, but in general a Mac app with no visible windows may actually take zero CPU, because (if it’s written to allow for it) the OS may kill the process entirely.
I would bet you couldn't use gmail from within the apple campus.