Viewerframe Mode Refresh Top -

.item padding: 20px; border-bottom: 1px solid #eee;

/* Ensure fresh renders start at top */ .viewerframe:mode-refresh scroll-behavior: auto; scroll-snap-type: none; viewerframe mode refresh top

Even if the user is halfway down, clicking the button executes scrollTop = 0 after the new data is in the DOM, guaranteeing the "top" behavior. Part 5: Advanced Use Cases & Optimization The basic implementation works, but production environments require nuance. Use Case 1: Infinite Scroll + Manual Refresh Top Platforms like Twitter allow infinite scroll but also a "See new Tweets" button. That button is a classic "viewerframe mode refresh top" pattern—but with a twist: it inserts new items at the top and optionally maintains relative position. That button is a classic "viewerframe mode refresh

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 Force mode to "refresh" setMode('refreshing'); // 3

setInterval(() => if (dashboardMode === 'auto_refresh_top') refreshTop(); , 5000); Even with a solid pattern, problems arise. Here is your troubleshooting guide. Issue 1: The "Scroll Flash" Symptoms: The viewerframe scrolls to top, then visually jumps down, then back up. Cause: Asynchronous rendering. The scrollTop = 0 runs before the new content is fully painted. Fix: Use requestAnimationFrame or setTimeout(..., 0) .