On Wednesday, 5 March 2025 at 05:23:20 UTC Chromestatus wrote: Contact emails g...@google.com
Explainer https://github.com/whatwg/html/issues/11070 Specification None Summary We propose to add a new render blocking token full-frame-rate to the blocking attributes. When the renderer is blocked with the full-frame-rate token, the renderer will work at a lower frame rate so as to reserve more resources for loading. An example use case of the proposed API will be: The web page contains an element <link rel="expect" href="#critical-content" blocking="full-frame-rate"/> in the page head. After parsing this element, the renderer will work at an implementation-specific lower frame rate. After the #critical-content element is parsed, the renderer will restore its frame rate. Maybe this is already the intent, but this should work in the same way as <link rel="expect" href="#critical-content" blocking="render"/>. As in, detecting #critical-content shouldn't be limited to the HTML parser (but yes, the element must not be in the parser's stack of open elements). The allows cases where #critical-content is added via JS. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8973f1ad-28a8-46fb-8f0f-95186ce8100dn%40chromium.org.
