Previous release notes for users coming from G3 and G4: We have investigated but have been unable to find a work around or fix so far. Upgrading to G5 resets custom container tabs in certain situations.Various preferences were incorrectly configured and these have now been changed.There was an issue when upgrading from G3 onward where your theme would get reset to default.You can now verify files downloaded from the downloads page, by appending.You can turn this off by typing about:config in the address bar, search for and toggle it to false. My GPU is a dated Kepler-based Nvidia Quadro, with drivers that Nvidia no longer keeps current.Waterfox’s custom look and feel now applies to all themes by default. Since Firefox 109 doesn’t have the same issue, it means primarily that they have been able to figure out the right combination of settings for certain thus affected GPUs, just like Google did with Chrome. When it comes to Firefox/Waterfox, I’ve just recently installed Firefox 109, for reference and comparison, and I’m not going to install 102 ESR along with it…īut there is no blur for me in Firefox 109 with ‘performance defaults’ enabled, while in Waterfox 5.1.2, I had to uncheck ‘performance defaults’ and uncheck ‘use hardware acceleration’. Interestingly enough, Microsoft has not gone through the same diligence with Edge, and I had to uncheck their ‘Use hardware acceleration’ option. While I’ve never observed this issue in any stable release of Google Chrome, it was well obvious to me from their detailed GPU-related settings that they have carefully disabled certain parts of GPU-accelerated rendering for certain GPU/drivers. I’m new to Waterfox, but I’ve known this blur for years from… Microsoft Edge!įrom what I’ve known, this has nothing to do with Windows dpi scaling and everything to do with the browser’s accelerated rendering incompatibility with certain GPUs and their drivers.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |