You cannot calculate pixel values โโwithout effectively setting CanContentScroll = "False".
To find out the size in pixels, you will need to create containers of all elements and summarize the heights of all containers. To do this, you must first create all the containers. This would mean that you actually lost virtualization and effectively set CanContentScroll = "False". In this case, why use CanContentScroll = "True" in the first place?
What Nikolaiโs code is trying to do is take responsibility for what CanContentScroll = "False" does, not giving you the smooth scroll that you might otherwise get.
More importantly, what problem does physical bias solve that you cannot solve with logical bias if you always know that CanContentScroll = "true"?
source share