Component Interop
we can navigate in one and have the other follow along. This can be set up by the component authors and is transparently available in apps. Try it out - navigate in sol-pod on the left and watch pod-os change on the right.
<sol-pod> file browser. Click a folder to open it.
<pos-*> shows whatever you open on the left.
This demo is one-way (Solid Web Components drives → PodOS follows). The
component-interop channel itself is two-way, but driving from the PodOS side needs the
host app's router: in a full PodOS app, clicking a folder updates the page URL
and the app re-points <pos-resource>. Embedded here with no router, a
PodOS-side click doesn't change pos-resource@uri or emit
pod-os:resource-loaded, so there's nothing to mirror back to swc — a PodOS routing
limitation, not an interop one.