on MacOS site gets "burned in" the transparency layer of the screen
Categories
(Core :: Graphics, enhancement, P3)
Tracking
()
People
(Reporter: tnwsx3jtnfiu31, Unassigned)
Details
Attachments
(1 file)
|
3.29 MB,
video/quicktime
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:79.0) Gecko/20100101 Firefox/79.0
Steps to reproduce:
opening any site and get a coffee or just leave the site open for a while. The site contrast will get "burned in" the transparency layer of the MacOS dark theme. Firefox is open on a 27" iMac and window is half-size to the left (split-view). dark mode is enabled on MacOS. Every app has a little transparency to catch up some colors from underneath and make the look of some greyish glass. So far so good, If firefoex is open with any website long enough, the contrast (boxes, big headings, images, ...) get "burned in" that transparency layer. If the heading is big enough, I can even read the heading, after I close firefox, by just simply opening finder and move it over the place where the heading was seen on the screen.
Actual results:
described above allready
Expected results:
there should be no burn in effect goin on, especially not after the app was closed.
| Reporter | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 3•6 years ago
|
||
Tentatively moving over to Graphics. Does this reproduce with any other apps and could this be a hardware issue? If not, could you run mozregression to see when this might have started happening?
If you have never run mozregression before, simply run these three commands in a Terminal window:
sudo easy_install pip
sudo pip install -U mozregression --ignore-installed
mozregression --good 2017-01-01
A number of Firefox versions will open in succession to narrow down when this started occurring. Simply type "good" or "bad" in Terminal based on whether or not a build reproduces the bug. Once finished, please post the output from the last run. It should give a last good and first bad revision as well as a link to look at the changesets in that range. Thank you!
Updated•6 years ago
|
Comment 4•3 years ago
|
||
Reporter, are you still experiencing this issue?
Comment 5•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit BugBot documentation.
Comment 6•2 years ago
|
||
Not actionable without more information from the reporter
Description
•