-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graphical glitches all over, firefox-125 #581
Comments
Hi @just-paja, Are you still experiencing this issue with Firefox 126? I'm not sure how Chameleon is affecting the browser UI like that. Have you tried disabling the resist fingerprinting option? |
Hello @sereneblue, thank you for coming back to me. I tried in firefox-126 and the problem still remains. However. after disabling the "Resist fingerprinting" option, it goes away. I'd expect the extension to avoid doing any changes to browser behaviour when it says that "it is off", but perhaps that might be just me misunderstanding the functionality :-) |
Hi @just-paja, Yes, I should clarify this in the wiki. Some options, when enabled, toggle Firefox browser settings. Disabling Chameleon through the Chameleon UI or using the whitelist only affect the browser profiles, injection and some of the standard options. Disabling the extension in the Firefox settings removes Chameleon's control of browser settings. |
Prerequisites
Expected Behavior
Graphics are rendered with lesser quality, but still "readable".
Current Behavior
With chameleon extension installed in firefox-125, the browser fails to render specific graphic elements even in the Firefox UI. All of these happen when the Chameleon extension is enabled in firefox and Chameleon itself is in disabled state. The problematic graphic elements are usually rendered as colorful vertical lines.
Some examples
I encountered more, but I figured that three examples should be enough. When I disable the extension in firefox extension manager, everything works as usual.
Relevant settings
This happens using the default settings (I used "Reset to default").
Context (Environment)
I actually switched graphic cards recently and the problem was both on nvidia and still persists on amdgpu.
The text was updated successfully, but these errors were encountered: