1.7 KiB
1.7 KiB
Current batch boundaries
Std_MainFullscreen now invokes the browser fullscreen API from the Web desktop adapter and passes the resulting window state to the native document view command. Browser refusal returns a failure. The native branch stores the actual boolean state, resets the active view mode to docked, and returns both values instead of assigning a fixed fullscreen marker.
Remaining integration boundaries:
- Fullscreen still needs active detached-view docking in the mounted view manager, synchronization after Escape, and recovery if the subsequent native request fails. The current path requires an open native document.
- Std_FreezeViews still assigns a frozen marker. Desktop camera capture, restore, clearing, and file save/load must replace it and reach the mounted camera.
- Std_HideObjects and Std_SelectVisibleObjects have native object visibility paths; view-provider visibility semantics remain unresolved. Std_HideSelection explicitly rejects subelement visibility.
- Std_TreeSingleDocument, Std_TreeSyncPlacement, Std_TreeSyncSelection, Std_TreeSyncView, Std_TreeViewActions, Std_ViewBoxZoom, Std_ViewCreate, and Std_ViewDock enter the native dispatcher, but their executable behavior and mounted consumers remain to be connected.
- Std_ViewDockUndockFullscreen has an adapter route but is absent from the inspected native command set. Std_ViewExample1 and Std_ViewExample2 are also absent from that set and need their actual scene behavior connected.
No registration markers were added. No tests, builds, browser validation, business acceptance, benchmarks, historical reconciliation, or receipts were run. The batch is incomplete; outer-pipeline receipts do not establish business acceptance.