I’ve recently written this post:
Hi Prefectionists! It’s only been a little over a week since the last release, but there are a lot of new features in Prefect 2.7, which was released just now. This release includes: Cancellation of flow runs Pause and resume of flow runs...
Reading time: 1 mins 🕑
Likes: 1 ❤
Which for one user resulted in the following email on his Superhuman email client being in dark mode:
The same worked well on my Android email app (Spark):
and on Gmail:
I’m aware it’s not easy to optimize for display across all possible clients, but is there perhaps some way to help that Superhuman user?
Thanks in advance.
We’ve had a few reports of a similar thing with mixed dark modes, though haven’t quite cracked a solution for Superhuman yet:
Apologies for the delay here, we have reproduced the issue in one specific scenario and merged a fix. If you are a hosted customer, the fix will be in your instance over the next week or so.
The specific scenario for the repro is using the default Outlook Web app running on an OS set to dark mode.
That combination caused some dark mode styles to apply to elements in the email template. That is because Outlook Web will respect @media (prefers-color-scheme:dark) (since OS is in dark…
I’ll pass this on to the engineer looking into it and they may reach out with a few questions for more info.
Thanks so much. Did you hear anything back? the issue persists
I gave them a nudge to see if there was new info, but the issue remains persistently stubborn.
Hopefully they can provide some updates soon.
I have some sad news
This issue is proving too tricky to track down and squish reliably across all the different emall clients, and I’m afraid Superhuman is one of the ones where we’re not going to be able to provide a fix.
I’m really sorry it’s not better news.
Same problem with Airmail.
Topics related :
Same problem with Skiff mail.
Here is the snapshot of the notification email sent when my post above was approved.
I’m having the same exact problem in Superhuman.
This doesn’t seem likely to be fixed anytime soon: