Open Bug 1680291 Opened 4 years ago Updated 4 years ago

Use -moz-default-appearance to compute glass margins on Windows 7, rather than analyzing the display list to find an opaque region

Categories

(Core :: Web Painting, task, P3)

Product:
Core
Component:
Web Painting
Platform:
All
Windows 7
Type:
task

Tracking

()

Status:
ASSIGNED

People

(Reporter: mstange, Assigned: mstange)

References

Details

On Windows 7, we tell the window manager which parts of the window need glass. The smaller the glass areas are, the better it is for performance.

At the moment, the glass region is computed from the window opaque region, which is assembled by FrameLayerBuilder as it processes the display list. That means it only works in non-WebRender (see bug 1680063), and is slower than necessary.

In contrast, on macOS, the vibrant region of the window is assembled from "theme geometry" information, which comes from -moz-default-appearance. This is simpler and works for both WR and non-WR.

We should make the Windows glass computation work more like the macOS vibrancy computation.

Severity: -- → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.