Bugzilla

(In reply to Erik Kurzinger from comment #24)
> I brought this up internally at NVIDIA. We provide a mechanism in our driver to apply certain settings for specific applications based on a json file https://download.nvidia.com/XFree86/Linux-x86_64/470.57.02/README/profiles.html and we agreed it would make sense to disable FXAA for firefox in the default configuration. FXAA really isn't expected to work well with something like a web browser anyway. Note that the environment variable mentioned in my last comment can serve as a work-around for the time being, but the app-profile solution will likely provide a better user experience.

Thanks for looking into it Eric!

Not FF related side note: there may be limits to the app-profile approach - GTK4 applications use GL rendering by default as well and a bunch of them currently get ported from GTK3, some of them coming with the next Gnome version this autumn.  While GTK could set the env variable, it may make sense to:
 - figure out some heuristic to disable the feature for "non-game" applications
 - make FXAA work better for such apps

(In reply to Erik Kurzinger from comment #24)
> I brought this up internally at NVIDIA. We provide a mechanism in our driver to apply certain settings for specific applications based on a json file https://download.nvidia.com/XFree86/Linux-x86_64/470.57.02/README/profiles.html and we agreed it would make sense to disable FXAA for firefox in the default configuration. FXAA really isn't expected to work well with something like a web browser anyway. Note that the environment variable mentioned in my last comment can serve as a work-around for the time being, but the app-profile solution will likely provide a better user experience.

Thanks for looking into it Eric!

Not FF related side note: there may be limits to the app-profile approach - GTK4 applications use GL rendering by default as well and a bunch of them currently get ported from GTK3, some of them coming with the next Gnome version this autumn.  While GTK could set the env variable, it may make sense to:
 - figure out some heuristic to disable the feature for "non-game" applications
 - make FXAA work better for such apps
 - provide a allow list instead of a block list - this is AFAIK how mesa deals with such features, notably `mesa_glthread`