Is "content-visibility:auto" relevant to speed up TW?

#1

content-visibilty:auto seems to achieve “lazy loading” by CSS, i.e things don’t load until brought into viewport.

The way it is generally discussed in the articles I’ve seen seems to mostly refer to images but just maybe it is generally useful also for tiddlers? Might it even be relevant to speed up native TW?

It is so far mostly for chrome - 73% global use

Here’s a nice writeup.

Here’s an article that gives a somewhat tiddlywiki-like example.

Import / Delete a Tiddler dynamically
#2

I recall playing around with using it to speed up the sidebar lists. The gains weren’t always consistent but I found no downside other than the need to specify heights in advance. I also make use of it in some custom components like my Notation editor and specially templated instances of Streams.

2 Likes
#3

contain and will-change might also be useful to improve performances: Helping Browsers Optimize With The CSS Contain Property | CSS-Tricks - CSS-Tricks, will-change | CSS-Tricks - CSS-Tricks

1 Like
#4

I’d guess these things, including content-visibility, only make sense on a system level. @saqimtiaz or @jeremyruston , has this been considered?

#5

Another thing I just came across that could speed up tiddlywiki (server), or at least improve the user experience : https://blurha.sh/

The idea is to associate a short string to an image, used to generate very quickly a blurred version of the image before the actual image finish to load. This prevent big white rectangle in image galleries.

I hope it’s not too out of topic @twMat !

1 Like
#6

Not at all. It’s a good addition.

1 Like