[optimization] "content-visibility" - do we already use it? should we?

[twMat]

I was peeking at the new CSS features and noted content-visibility (which is a few years old but now has good coverage).

As described by css tricks

Think of it sort of like lazy loading in the sense that an off-screen element’s children are not rendered until they enter the viewport. [...] The results can be dramatic.

Relevant for TW? Already in use?

add: anoter css article

[pmario]

With v5.4.0 we defined ES2017 as the target JavaScript, CSS, HTML version. content-visibility is supported since late 2024 by all major browsers.

see: #9113

Click the "Date relative" button at caniuse-com, to see the overview

[Jermolene]

With v5.4.0 we defined ES2017 as the target JavaScript, CSS, HTML version. content-visibility is supported since late 2024 by all major browsers.

Worth noting that ES2017 does not cover CSS or HTML. CSS is tricky because it is no longer versioned; individual modules are versioned instead:

https://www.w3.org/Style/CSS/current-work

[Jermolene]

Hi @twMat that's an excellent idea, and it would be good to explore using it in v5.4.0, applying it to the tiddler wrapper in the story river. It won't have any effect on older browsers so seems safe from a backwards compatibility perspective.

[saqimtiaz]

I have been using this for a while to speed up the sidebar lists, but it is of very limited usefulness when you do not know in advance the size of the element you are using it on.

[twMat]

@saqimtiaz - just so it is not missed; that last article I noted in the OP is about the issue you bring up.