You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: specs/WindowControlsOverlayConfiguration.md
+15-9
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,10 @@ The overlay Settings lives on the controller object.
10
10
11
11
This API is designed to be used in addition with the other non-client region APIs
12
12
and features. These include `app-region: drag`, and `IsNonClientRegionSupportEnabled`.
13
+
14
+
# Conceptual pages (How To)
15
+
Here is a concept doc on the window controls overlay: https://wicg.github.io/window-controls-overlay/#concepts. This was written for the PWA counterpart for this feature. From the perspective of HTML & Javascript layers, everything there applies in Webview2 as well.
/// The Overlay buttons will sit on top of the HTML content, and will prevent mouse interactions
99
103
/// with any elements directly below it, so you should avoid placing content there.
100
-
/// To that end, there are four CSS environment vairables defined to help you
104
+
/// To that end, there are four [CSS environment vairables](https://developer.mozilla.org/en-US/docs/Web/API/Window_Controls_Overlay_API#css_environment_variables)
105
+
/// titlebar-area-x, titlebar-area-y, titlebar-area-width defined to help you
101
106
/// get the dimensions of the available titlebar area to the left of the overlay.
102
107
/// Similarly the navigator object wil contain a [WindowControlsOverlay property](https://developer.mozilla.org/en-US/docs/Web/API/WindowControlsOverlay)
103
108
/// which can be used to get the titlebar area as a rect, and listen for changes
0 commit comments