Top | Viewerframe Mode Refresh

deliberately avoids this unpredictable reset. Instead, it declares a specific, predictable behavior: Every manual or timed refresh forces the frame to reset to the top. This sounds counterintuitive, but for certain use cases (e.g., news headlines, dashboard KPI cards, or image galleries), it is the cleanest UX pattern. Part 3: Core Architectural Patterns Implementing "viewerframe mode refresh top" requires a specific architecture. Below are the three primary patterns developers use. Pattern A: The Controlled Scroll Reset (Manual Mode) This is the purest form of the keyword. The viewerframe is explicitly in "top mode."

function Viewerframe( data ) const frameRef = useRef(null); const refreshAndGoTop = () => // 1. Refetch data refetchData(); // 2. Force mode to "refresh" setMode('refreshing'); // 3. After DOM update, scroll frame to top setTimeout(() => if (frameRef.current) frameRef.current.scrollTop = 0; // The "top" command viewerframe mode refresh top

Symptoms: scrollTop = 0 doesn't work on iOS. Fix: Scroll the body or use window.scrollTo(0,0) on the frame’s parent. Mobile Safari requires -webkit-overflow-scrolling: touch; . Part 7: Performance Metrics Why should your team adopt "viewerframe mode refresh top"? Measure these KPIs: deliberately avoids this unpredictable reset