also looking at this
feat: portable typed window controls on Linux and Windows
#326
9 files
+652
-32
| @@ -137,12 +137,12 @@ The next multi-window milestone needs product decisions in addition to code: | ||
| 137 | 137 | application-level asynchronous source above. |
| 138 | 138 | 3. Decide whether Touch Bar should stay primary-window scoped or follow the |
| 139 | 139 | key window with separately owned item definitions and callbacks. |
| 140 | 4. Finish advanced Linux/Windows window actions and clarify which are portable | |
| 141 | versus platform-specific, without conflating close semantics: macOS retains | |
| 142 | a closed page, while Linux and Windows release it. | |
| 143 | 5. Expand platform-native integration beyond the current named-window lifecycle | |
| 144 | smokes. CI runs Linux WebKitGTK under Xvfb and Windows WebView2 on a native | |
| 145 | runner, but advanced actions and packaged-app behavior still need coverage. | |
| 140 | 4. Decide the portability contract for advanced actions beyond bounds, | |
| 141 | centering, resizability, size limits and fullscreen. Closing still differs: | |
| 142 | macOS retains a closed page, while Linux and Windows release it. | |
| 143 | 5. Expand platform-native integration beyond named-window lifecycle and core | |
| 144 | geometry/control smokes. CI runs Linux WebKitGTK under Xvfb and Windows | |
| 145 | WebView2 on a native runner; packaged-app behavior still needs coverage. | |
| 146 | 146 | |
| 147 | 147 | ## Review checklist |
| 148 | 148 | |