also looking at this
feat: add Linux and Windows named-window routing
#325
29 files
+2250
-200
| @@ -330,15 +330,16 @@ await settingsWindow.focus() | ||
| 330 | 330 | ``` |
| 331 | 331 | |
| 332 | 332 | Calling `createWindow` again with the same `id` brings the retained native |
| 333 | window forward and returns the same typed handle. Runtime creation currently | |
| 334 | uses the macOS host. `close()` retains that page for a later reopen, while | |
| 335 | `destroy()` permanently releases a runtime-created window; the unnamed primary | |
| 336 | window is not destroyable through this API. Modal and parent-window | |
| 337 | relationships are not supported. | |
| 333 | window forward and returns the same typed handle on macOS, Linux, and Windows. | |
| 334 | On macOS, `close()` retains the page for a later reopen. On Linux and Windows, | |
| 335 | closing releases the native page; reopening the same ID creates a fresh one | |
| 336 | behind the stable typed handle. `destroy()` permanently releases a | |
| 337 | runtime-created window; the unnamed primary window is not destroyable through | |
| 338 | this API. Modal and parent-window relationships are not supported. | |
| 338 | 339 | |
| 339 | 340 | The [multi-window ownership contract](architecture/multi-window-ownership.md) |
| 340 | 341 | tracks which state is window-scoped, which events intentionally target the |
| 341 | primary page and what remains before the feature is cross-platform. | |
| 342 | primary page, and which advanced behaviors remain outside the contract. | |
| 342 | 343 | |
| 343 | 344 | ### Window Lifecycle Events |
| 344 | 345 | |