(In reply to lexlexlex from comment #57) > The result of my testing shows that it makes my Firefox run at the wrong refresh rate. Yes, that's a known issue and may get fixed by bug 1728473, bug 1728473 or by switching to Wayland. As you said, your configuration needs a workaround either way. You will still be able to stick to your current configuration by setting `gfx.x11-egl.force-disabled:true` additionally to `layout.frame_rate:0`. However, as there's currently no perfect solution, having non native refresh rate is IMO better than having windows getting stuck - as default configuration. Especially as many users don't have > 60Hz displays.
Bug 1716049 Comment 59 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to lexlexlex from comment #57) > The result of my testing shows that it makes my Firefox run at the wrong refresh rate. Yes, that's a known issue and may get fixed by bug 1728473, bug 1640779 or by switching to Wayland. As you said, your configuration needs a workaround either way. You will still be able to stick to your current configuration by setting `gfx.x11-egl.force-disabled:true` additionally to `layout.frame_rate:0`. However, as there's currently no perfect solution, having non native refresh rate is IMO better than having windows getting stuck - as default configuration. Especially as many users don't have > 60Hz displays.