I'm not familiar with details of rendering such as 'direct scanouts', but a few quick questions:
- Did this work as expected with earlier GNOME versions? - Is it only Firefox (snap?) that is affected, or are other applications/snaps affected too? Depending on the above and whether it's a GNOME, firefox, or snapd bug, it may be appropriate to open an issue on Mozilla's tracker https://bugzilla.mozilla.org and link it to this bug here for tracking purposes. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2078774 Title: Fullscreen Firefox is not being rendered as direct scanout in GNOME 47 Status in firefox package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Fullscreen Firefox is not being rendered as direct scanout in GNOME 47. Press Alt+F2, type "lg", click Flags and enable PAINT_DAMAGE_REGION. This will show you in red when part of the screen is being composited. When an app is getting fullscreen direct scanout, all redness should go away. It does for Chrome, but not for Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2078774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
