Change the pref name in anticipation of removing it completely
to see what the fallout will be.

Change the pref name in anticipation of removing it completely
to see what the fallout will be.

https://hg.mozilla.org/mozilla-central/rev/6c23b14b93f8

(In reply to Jeff Muizelaar [:jrmuizel] from comment #0)

Change the pref name in anticipation of removing it completely
to see what the fallout will be.

removing it completely

I want to add that Compositing of WebRender is still more bugged then Compositing of Direct3D 11. One of the biggest issue for me is that, the WebRender is using grayscale anti-aliasing instead of sub-pixel anti-aliasing for rendering fonts in more places than Direct3D 11. This makes fonts blurry, fuzzy and unsharp.
What's more having option to disable WebRender, same as it's possible to force disable Direct3D 11, it's very useful for debugging and testing.
Please reconsider this plan, at least for near future. Thank you very much in advance.

Right now Nvidia/Linux users have to manually disable WebRender if they want to have multiple windows with acceptable framerate.
bug 1720634: Framerate of a window seems to be limited to "60 Hz divided by count of windows with changing content". If you have 3 windows open, each is limited to 20Hz.