Viewerframe Mode Refresh |work| Official

Viewerframe Mode Refresh

Viewerframe Mode Refresh is a feature update that improves how embedded content is displayed and kept up to date in applications that use viewer frames (iframes, embedded viewers, or preview panels). This article explains what the refresh does, why it matters, and how to implement and troubleshoot it.

2. Why a Dedicated Refresh is Required

| Issue | Consequence of no mode refresh | |-------|--------------------------------| | Shader switch | Wrong lighting or missing textures | | Layout toggle | Overlapping viewports or incorrect aspect ratios | | Color space change | Faded or over-saturated output | | LOD (level of detail) change | Pop-in or low-res assets in high-res mode | | Frame buffer accumulation | Ghosting or motion blur from previous mode | viewerframe mode refresh

A mode refresh is not a full scene reload. It is a targeted pipeline reset. Viewerframe Mode Refresh Viewerframe Mode Refresh is a

Parameter C: `preserve_framerate`

True: The refresh tries to maintain the original FPS (e.g., 60fps) even if refresh takes 16ms.
False: The refresh happens immediately, which may visually "skip" as few frames.

Performance considerations

Prefer soft re-render when possible; reserve hard reload for structural changes.
Debounce refresh triggers (e.g., 200–500 ms) to avoid thrashing.
Use caching, ETags, and conditional requests to reduce network load.
Lazy-load heavy subcomponents after initial soft refresh.

Viewerframe Mode Refresh |work| Official