Bug 1617002 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

Working on culling in Mutter (Gnome Shell), testing different applications.

Exact steps: 
 - use Mutter >= 3.35.91
 - use the Wayland session
 - start `weston-simple-damage --verbose` in a terminal (part of Weston demo clients)
 - hide the demo app behind other applications
 - if the application sets an opaque region or doesn't have an alpha channel, `weston-simple-damage` will get culled out, therefore not receive frame callbacks any more -> output in terminal stops


Actual results:

demo app gets culled out behind Firefox on Wayland (basic, ogl, Webrender) and X11 (basic, ogl)

demo app does *not* get culled out behind Firefox X11 Webrender


Expected results:

Should get culled out, too.

I did some testing quick testing in nightly and apparently there's nothing wrong in the part in `nsWindow.cpp` (it sets the region and does not unset it). On resize, Mutter first receives a valid region and then `NULL` again. Now I'm stuck.
Summary: when using WR we always use textures with alpha channel. Thus we need to set an opaque region to let the OS compositor know that it can skip painting everything behind the FF window (minus rounded corners). This is already implemented but does not work properly on X11 atm.

---

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

Working on culling in Mutter (Gnome Shell), testing different applications.

Exact steps: 
 - use Mutter >= 3.35.91
 - use the Wayland session
 - start `weston-simple-damage --verbose` in a terminal (part of Weston demo clients)
 - hide the demo app behind other applications
 - if the application sets an opaque region or doesn't have an alpha channel, `weston-simple-damage` will get culled out, therefore not receive frame callbacks any more -> output in terminal stops


Actual results:

demo app gets culled out behind Firefox on Wayland (basic, ogl, Webrender) and X11 (basic, ogl)

demo app does *not* get culled out behind Firefox X11 Webrender


Expected results:

Should get culled out, too.

I did some testing quick testing in nightly and apparently there's nothing wrong in the part in `nsWindow.cpp` (it sets the region and does not unset it). On resize, Mutter first receives a valid region and then `NULL` again. Now I'm stuck.

Back to Bug 1617002 Comment 0