Open Bug 1494058 Opened 2 years ago Updated 5 months ago
Colored Artifacts Appear Above Tab Bar with OS X Mojave in Dark Mode
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180920135444 Steps to reproduce: Enable OS X Dark Mode Theme. Enable Firefox Dark Theme. Browse the web with multiple tabs open. Actual results: A magenta, red and yellow artifact can be seen at the edge of the 'chrome' above the tab selection bar. It catches ones eye since it contrasts with the dark theme. Unknown if this is an OS X issue, or a Firefox issue. The issue is also difficult in that I have not found a deterministic reproduction step sequence. Attempting to capture this with the built in screen recorder on OS X disrupted the dot flashing behavior. Instead see attached video screen capture from a phone. Expected results: No graphical anomalies or artifacts appear.
Summary: OS X Mojave Dark Mode Artifacts Appear → Colored Artifacts Appear Above Tab Bar with OS X Mojave in Dark Mode
Picture of the example artifacts that appear.
Video of the artifacts behavior. https://youtu.be/Y1QbrW1aZWQ
Component: Untriaged → Widget: Cocoa
Product: Firefox → Core
Are you still able to reproduce in the most recent Nightly? https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly
Priority: -- → P2
(In reply to Stephen A Pohl [:spohl] from comment #3) > Are you still able to reproduce in the most recent Nightly? > https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly I will begin this test - I will say after 20 minutes no sign. This is inconclusive. Any suspicion of a change affecting this?
(In reply to Stephen A Pohl [:spohl] from comment #3) > Are you still able to reproduce in the most recent Nightly? > https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly This has occurred again with the latest nightly.
I and some other people have also been seeing this glitch, which is also sometimes grey or green. I've managed to capture it on a screen recording: https://www.youtube.com/watch?v=VsdftF8YaZ8 Although browser-like applications like Firefox seem especially likely to trigger it, I've seen it in Firefox, Atom (Electron), Discord (Electron), and iTerm. This leads me to believe the bug is likely in Apple's OS code, or it is somehow triggered by something these applications are doing. Here's a Stack Exchange Q&A on the issue: https://apple.stackexchange.com/q/338319/70505
Oh one other thing. I was able to reproduce it in Light Mode, it just requires Firefox to still use a dark theme.
Some more information as I continue to better understand this glitch. I've had pretty consistent success reproducing the bottom-edge version of this glitch using: - Firefox Developer Edition (default dark theme) - Developer tools panel open and docked to the bottom of the window (default dark dev tools theme) - With the Console tab open or Split Console active (puts a nice dark area on the bottom of the window) - Browsing to any website like http://example.com - Refreshing the page until it appears Some other tidbits: - It only seems to happen when the integrated graphics are in use. I've been unable to reproduce with the discrete card active. - If I suspend the firefox and plugin-container processes over SSH while the glitch is happening using kill -SIGSTOP, the glitch continues flashing, indicating the glitch is outside the Firefox processes. - Going further, I tried systematically suspending processes over SSH, to see which one might be responsible. The only one suspending causes the flashing to freeze with was WindowServer.
Just to let everyone know, for reasons outlines in the linked Stack Exchange Q&A (in particular QuickTime can record it, but Digital Color Meter and Pixie cannot see it), I'm fairly certain this is actually an OS bug. I filed a bug report with Apple on November 14th, but haven't heard anything back about it since. If anyone has any pull with Apple, the Problem ID is: 46079638
At some point recently Apple marked my bug report as a duplicate of 45841204 so I guess they were already aware of the issue. It was not resolved in 10.14.2.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.