After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 696805 - GtkWindow should set the opaque region for the content window when possible
GtkWindow should set the opaque region for the content window when possible
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Low enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-03-28 18:58 UTC by Kristian Høgsberg
Modified: 2013-09-03 16:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kristian Høgsberg 2013-03-28 18:58:37 UTC
The wayland protocol lets clients set a surface region to indicate that that region contains all opaque pixels.  The idea is that in the common case, most apps have rounded corners and drop shadows, but in the center is a big opaque rectangle.  If the compositor knows about that region, it can optimize rendering to not paint surfaces below the opaque region and turn off blending.

In the general case, this may be expensive to compute and there's also the discussion of how fine-grained the region should be vs how many opaque pixels it covers.

For the typical window, there will be a big opaque rectangle in the middle that we can communicate to the compositor.