Full Desktop Window Support

Created: 1776211364 Priority: B Status: doing Description: After the implementation of dynamic instancing, but before cross-origin PWA, implement restored windows on desktop.parts. Consider having other hosts in the Demo Ecosystem forward back to desktop.parts. Restored windows have their own subpermutation over the pinned (task bar) apps permutation. Note: an open app is actually just an app which is pinned to the task bar, but only those pinned apps can be viewed. These pinned tasks should be able to be reordered by dragging and dropping. Title bars should have a restore button. The desktop application should become an abstract which can be extended to create a desktop at any address so that framework users can implement all of their apps in a single domain if they want. Consider a "maximized on open" setting (or, conversely, a default window state) so that apps which are not currently pinned are opened into the given configuration as they are pinned. Forwarding all domains to the desktop (while pinning the apps that were just visited, especially if pinned maximized) would eliminate cross-origin full-screen and PWA problems. Consider if full-screened apps should have taskbar and titlebar visible. The presentation of sites on first visit should be considered - users won't know that it is an overall desktop they are visiting or this could distract them from the specific domain's intended content. Canonical links and SEO per-domain must still be handled correctly. Consider if an unopened task can be dragged from the menu and/or desktop in order to open it (pin and view it). Restored windows should be movable and resizable. Affected Parts: ecosystem, desktop.parts, task-bar.desktop.parts, windows.desktop.parts Linked Issues: Complete Operating SystemBdoingApr 15, 2026Cross-Origin PWABdoingApr 14, 2026Add Dynamic PartsCdoingApr 14, 2026