Files
FreeCADWasmDev/docs/current/web-commandwindow-boundary.md
wangdequan 9a7c4f0335 Save FreeCAD Web workspace sources and user validation evidence
IFC native binding remains incomplete; preserve accurate test results.
2026-09-15 22:01:58 +08:00

25 lines
1.3 KiB
Markdown

# Web CommandWindow Boundary
Batch: `890fd2edecd5bf5d51905062`
The native standard-command handler in
`freecad-source/src/WebAssembly/FreeCADCoreProbe/WebViewCommands.h` now accepts
`Std_ActivateNextWindow`, `Std_ActivatePrevWindow`, `Std_CascadeWindows`, and
`Std_CloseActiveWindow`. It invokes the registered FreeCAD GUI command after
checking the main window and command availability. The supplied desktop source
in `src/Gui/CommandWindow.cpp` delegates these operations to the main window.
Native window ordering, layout, and close vetoes remain owned by that code.
The response reads the active document after invocation; invocation does not
assert that a close was accepted.
Remaining boundary: the existing application registrations use
`web.standardCommand`. End-to-end transport to this handler and availability of
the native GUI main window in the loaded Web runtime have not been established.
Without that host the handler returns `gui_host_unavailable`; this change does
not supply a browser window manager or establish completion of these workflows.
The next implementation batch must connect the mounted window owner to native
window operations through the actual standard-command route.
No tests, builds, browser validation, benchmarks, or acceptance were run.
Build, sync, and route receipts remain owned by the outer pipeline.