mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-20 16:55:40 +00:00
c0cdef1454
This code was assuming that the only non-opaque parts of compositor rendering would be the parts of the window that had vibrancy. But now that the default window background is transparent, we can have non-vibrant parts where we render into transparency. Dialog windows such as sheet windows are an example of this. So instead of using the non-vibrant region of the window as its opaque region, we now use the region that is covered by opaque Gecko layers. This region is a lot more conservative: For example, the main browser chrome is now entirely transparent, because the chrome's opaque parts share a layer with its transparent parts. As a result, this change slightly affects the CALayer partitioning in the main browser window: The entire browser chrome is now transparent, not just the tab bar. The web content area is still opaque. I think this will be fine. The thing I'm most concerned about is that scrolling inside web content might cause invalidations of pixels from the chrome, because then we'd recomposite the CALayers that cover the vibrant tab bar. This doesn't seem to happen most of the time though, from what I can tell. Differential Revision: https://phabricator.services.mozilla.com/D51466 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| 2d | ||
| angle | ||
| cairo | ||
| config | ||
| docs | ||
| gl | ||
| graphite2 | ||
| harfbuzz | ||
| ipc | ||
| layers | ||
| ots | ||
| qcms | ||
| sfntly | ||
| skia | ||
| src | ||
| tests | ||
| thebes | ||
| vr | ||
| webrender_bindings | ||
| wr | ||
| ycbcr | ||
| moz.build | ||