Live View base URL configuration for SPA routing

Live View base URL configuration for SPA routing

Dreamweaver 2021 and later documents Live View as real-time preview for HTML, CSS, and JavaScript. The relevant configuration gap is a preview origin: Adobe's documentation does not describe a base URL or reverse-proxy setting for loading an SPA from a local development server.

Live View is understood to render local documents in a Chromium Embedded Framework through the file:// protocol. That origin can conflict with client-side routers that call pushState or replaceState, although the exact behavior must be confirmed for the CEF version bundled with each Dreamweaver release. Hash routing changes URL semantics, while External Browser changes the preview target and may not preserve Live View's DOM inspection and CSS Designer integration.

The design goal is to decide whether Live View should accept a configurable preview origin while retaining its IDE inspection tools. The relevant release-specific check is whether a History API transition behaves differently under file:// and an http://localhost origin.

• Should Dreamweaver expose a base URL for Live View, including reverse-proxied path prefixes?
• Which behavior in currently supported releases should define the compatibility baseline?