CSS Designer and Live View: Reconciling Duplicate Rules with Cached Computed Styles

When working in Dreamweaver, the CSS Designer panel can emit duplicate rules for the same selector during vendor auto-prefixing, yet the application offers no documented preference to merge or suppress those duplicates. At the same time, Live View may present computed styles that differ from Design view because of internal preview caching, and there is no explicit refresh control exposed in the UI to force a reconciliation.

For teams maintaining stylesheets across Dreamweaver CC 2022 through 2024, the integration boundary between CSS Designer's rule generation and Live View's rendering cache creates ambiguity: which representation should be treated as authoritative when duplicates appear in the panel and the preview does not match Design view? Without a documented consolidation setting or cache-refresh command, developers must decide whether to manually edit the stylesheet or rely on preview behavior that may vary by release.

Is there a supported workflow to consolidate duplicate auto-prefixed rules produced by CSS Designer without manually editing the source? Does Live View expose any hidden or documented mechanism to invalidate its computed-style cache when Design view and Live View diverge? How do Dreamweaver CC 2022–2024 release notes address the interaction between CSS Designer auto-prefixing and Live View preview caching?