Google has called this property out in https://web.dev/articles/dom-size-and-interactivity#use_the_content-visi... and our initial render timing findings on pages with an extreme number of hidden-by-default DOM nodes is quite dramatic.
The `content-visibility` property will prevent user-agents from evaluating certain DOM nodes and descendants based on a heuristic.
Since DOM node evaluation may be skipped by this property, the usual rules applied by things like `display: none` and `visibility: hidden` may not function like one would expect them to! It may become necessary to manually apply other attributes to the DOM (i.e. `aria-hidden`) in order to remove elements from the accessibility tree!
None
None
None
Active
11.0 🔥
Clarified accessibility considerations with an example.
Bumping to major, this is potentially a significant improvement and I think we should try to do something in core - entity listings, layout sections, and comments seem like good candidates as well as hamburger menus as listed in the summary.