To answer myself: no, at least not for the following test case: 10-15 windows with vsynctester.com running. Neither with WR nor basic do I get 60 fps, neither does chromium. On gnome wayland with `MOZ_ENABLE_WAYLAND=1` it's no problem at all, however (with FF >= 86) :/ It could, however, be that `OcclusionStateChanged()` does less than we do on Wayland. E.g. `requestAnimationFrame()` still fires on X11 on fluxbox while it doesn't on Wayland. Markus, does `OcclusionStateChanged()` stop `requestAnimationFrame()` when hidden on MacOS?
Bug 1693513 Comment 32 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
To answer myself: no, at least not for the following test case: 10-15 stacked maximized windows with vsynctester.com running. Neither with WR nor basic do I get 60 fps, neither does chromium. On gnome wayland with `MOZ_ENABLE_WAYLAND=1` it's no problem at all, however (with FF >= 86) :/ It could, however, be that `OcclusionStateChanged()` does less than we do on Wayland. E.g. `requestAnimationFrame()` still fires on X11 on fluxbox while it doesn't on Wayland. Markus, does `OcclusionStateChanged()` stop `requestAnimationFrame()` when hidden on MacOS?
To answer myself: no, at least not for the following test case: 10-15 stacked maximized windows with vsynctester.com running. Neither with WR nor basic do I get 60 fps, neither does chromium - on fluxbox. On gnome wayland with `MOZ_ENABLE_WAYLAND=1` it's no problem at all, however (with FF >= 86) :/ It could, however, be that `OcclusionStateChanged()` does less than we do on Wayland. E.g. `requestAnimationFrame()` still fires on X11 on fluxbox while it doesn't on Wayland. Markus, does `OcclusionStateChanged()` stop `requestAnimationFrame()` when hidden on MacOS?