11-27-2024 05:08 AM
The program Glass2K which allows you to make any window transparent no longer works correctly with Firefox since 133.0. Now, whenever I make Firefox transparent, regardless of 10%, 90% or anywhere in between, Firefox no longer visually updates to anything I do, such as changing tabs, clicking a link, typing etc. until I remove the transparency effect. It still functions normally, I just don't see what's happening while the transparency is in effect.
I had been using Glass2K with Firefox for around a year with no issues on any previous version. Is there perhaps a new feature causing this which I could disable? Or is this just a bug? I'd appreciate if this could be looked in to. Thank you
Solved! Go to Solution.
11-30-2024 01:03 PM - edited 11-30-2024 01:04 PM
Found the issue. I need to select the 'Use hardware acceleration when available' box (or possibly just 'Use recommended performance settings' would do) and Glass2K works again.
The reason I didn't find this out initially when matching the test profile settings to my default was because it requires a restart of Firefox for the change to take effect. Simply opening a new tab and/or Ctrl+F5ing isn't enough, which is all I'd tried yesterday.
Thanks jscher2000, you helped lead me in the right direction.
11-28-2024 04:54 PM
This freeware from 2017? https://www.majorgeeks.com/files/details/glass2k.html
If you have an hour to investigate, you can use the Mozregression tool to see what change in Firefox caused this. https://mozilla.github.io/mozregression/
After installing, run the program and tell it you want to test by release, with the last good release being 132 and the first bad release being 133. It then will download intermediate builds you can test to see which one caused the incompatibility. And then finally, file a bug with the results of the regression test at https://bugzilla.mozilla.org/.
11-29-2024 11:24 AM
Yes that's the correct freeware.
Thank you for the advice. I installed and tried out Mozregression but every build option it gave me worked fine, even going all the way from the beginning of 132 to the most recent build, setting today as the date of first bad build (had initially tried the actual correct date of 27th but expanded when that failed to find a bad build).
Could there be something else causing the issue which Mozregression wouldn't show? The issue persists even without any extensions, and on a fresh window with no tabs, even on a new private window. Any more ideas?
11-29-2024 11:35 AM
Could there be a difference in graphics settings between the development builds and the regular release? You would expect the regular release to be the most stable configuration, but maybe something got turned on or off in your regular profile that we're not accounting for.
11-29-2024 01:29 PM - edited 11-29-2024 02:09 PM
So it definitely seems to be something to do with my profile. I created a new test profile and opened a separate window for it, and I don't get the issue there. I went in to settings and extension/theme/plugin settings and set everything as close as possible on both profiles (there are slightly different options for whatever reason), and my regular profile still has the issue but the test profile doesn't. No luck figuring out the cause so far.
EDIT: In terms of 'Graphics' settings on the 'about:support' page, it's the same on both profiles other than GPUProcessPid (5176 on default vs 10244 on test).
11-30-2024 01:03 PM - edited 11-30-2024 01:04 PM
Found the issue. I need to select the 'Use hardware acceleration when available' box (or possibly just 'Use recommended performance settings' would do) and Glass2K works again.
The reason I didn't find this out initially when matching the test profile settings to my default was because it requires a restart of Firefox for the change to take effect. Simply opening a new tab and/or Ctrl+F5ing isn't enough, which is all I'd tried yesterday.
Thanks jscher2000, you helped lead me in the right direction.