Which practice helps prevent layout thrash when the Blk Dot Menu updates frequently on a high-traffic app?

Which practice helps prevent layout thrash when the Blk Dot Menu updates frequently on a high-traffic app?

• A. Using lazy-loading for heavy items and avoiding heavy DOM updates.
• B. Rebuilding the DOM on each update.
• C. Animating all changes.
• D. Caching nothing.

Answer: (A)

Layout thrash happens when frequent DOM updates force the browser to reflow layout many times in quick succession. The best way to prevent this in a high-traffic app is to keep updates lean and defer or reduce what the browser has to calculate. Using lazy-loading for heavy items cuts down the number of elements that participate in the layout, so each update touches fewer nodes and triggers fewer reflows. Coupled with avoiding heavy DOM updates—meaning batch changes, schedule writes together (for example with a single animation frame), and minimize touching the DOM for every small change—the browser can stabilize layout and paint fewer times, which keeps the UI responsive even as updates come in rapidly. Rebuilding the DOM on every update would force a full reflow each time, amplifying thrashing. Animating all changes can cause continuous repaints and still engage layout calculations for movement, potentially increasing churn. Caching nothing offers no benefit in reducing work or layout recalculation, so it doesn't help with thrash.

Layout thrash happens when frequent DOM updates force the browser to reflow layout many times in quick succession. The best way to prevent this in a high-traffic app is to keep updates lean and defer or reduce what the browser has to calculate. Using lazy-loading for heavy items cuts down the number of elements that participate in the layout, so each update touches fewer nodes and triggers fewer reflows. Coupled with avoiding heavy DOM updates—meaning batch changes, schedule writes together (for example with a single animation frame), and minimize touching the DOM for every small change—the browser can stabilize layout and paint fewer times, which keeps the UI responsive even as updates come in rapidly.

Rebuilding the DOM on every update would force a full reflow each time, amplifying thrashing. Animating all changes can cause continuous repaints and still engage layout calculations for movement, potentially increasing churn. Caching nothing offers no benefit in reducing work or layout recalculation, so it doesn't help with thrash.