The new CSS property that boosts your rendering performance (web.dev)
4 points by cmpit 1 hour ago
> Last updated 2020-08-05 UTC.
For those who were wondering, it is available more broadly [0] than it was when the article was written (2020).. 75+%, almost 85% on tracked desktop.
Containment spec, which `content-visibility` is built on top of, reaches around 95%, (98% mobile) [1].
For content-visibility, once again IOS Safari proves to be the IE of our time.. ;(
(perhaps ironically, Microsoft Edge supported it fully four years before Apple got around to it.)
why is a manual property needed. why is the browser engine not able to figure out what is off-screen?
Because of inline css and different fonts on different os-es and generally no guarantees about render size. In short, you have no idea how big a block is without rendering it.
That would be a good point, as the C in CSS should stand for complicated, but this recommended setting is "auto" (changed from the default of "visible"). Setting it to auto turns on layout containment, style containment, and paint containment for the element. It allows the browser to skip rendering but still keep the elements available to, e.g. tab order. It's like a hybrid of visible and hidden.
https://www.w3.org/TR/css-contain-2/#content-visibility
I think the answer to the GP's question is that the browser does know how to compute this before starting the render pass, but the additions to the spec that allow for placing fences around the layout- and style-related containment was too new for all browsers yet, so the default is to assume all rendering is done, and the HTML/CSS author can opt in to turning this on (which in early days may have had the risk of bugs in implementation or inconsistencies across browsers).
The design of CSS is such that pretty much any element in the document can affect any other element. Therefore determining what is off-screen generally requires processing the entire document.
The manual property changes the behavior of CSS so that elements in a subtree cannot affect elements outside the subtree, allowing the browser to quickly discard whole subtrees instead.
Great, lazy loading without JS
Unrelated to the content: who had the idea to machine-translate programming posts? The property name the post is about is localized for me, which makes no sense at all.
Same here, the post was in really bad French and was impossible to understand before I found on the page how to show the original version.
Microsoft also translates documentation based on my IP and it’s atrocious