api8.top ww.html,HTML

Rendering opportunities: Remove from docs all browsing context do not have a

rendering opportunity.

A browsing context has a rendering opportunity if the user agent is

currently able to present the contents of the browsing context to the user,

accounting for hardware refresh rate constraints and user agent throttling for performance

reasons, but considering content presentable even if it's outside the viewport.

Browsing context rendering

opportunities are determined based on hardware constraints such as display refresh

rates and other factors such as page performance or whether the page is in the background.

Rendering opportunities typically occur at regular intervals.

This specification does not mandate any particular model for selecting

rendering opportunities. But for example, if the browser is attempting to achieve a 60Hz

refresh rate, then rendering opportunities occur at a maximum of every 60th of a second (about

16.7ms). If the browser finds that a browsing context is not able to sustain this

rate, it might drop to a more sustainable 30 rendering opportunities per second for that

browsing context, rather than occasionally dropping frames. Similarly, if a

browsing context is not visible, the user agent might decide to drop that page to

a much slower 4 rendering opportunities per second, or even less.