You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Firefox has a nasty bug (https://bugzilla.mozilla.org/show_bug.cgi?id=373875) that breaks any attempt of assigning big numerical values to css properties. Since the virtual list does exactly that to give the illusion of a very big list without actually loading the components, you might run into that bug for very big lists. Unfortunately, I haven't found a way to work around it yet.
If I understand the problem correctly, in the past I've worked around this by having multiple "spacer" elements in the DOM which are of the maximum size. As long as no single element is bigger than the maximum height, this seems to work. So instead of setting the container element to 1,000,000 px (for example), you have multiple spacer children which are each 10,000 px for example. The spacer elements and the actual elements that are shown will together add up to 1,000,000 px. Hope that makes some sense!
IE also has the same issue btw (not sure about Edge).
The text was updated successfully, but these errors were encountered:
Browsers still tend to do weird things when your container has elements that exceed a certain height. I'd rather these tools "do the right thing" rather than implement quirks to get around issues with the rendering engine.
What would the right thing be in this scenario? Right now this library will break when you attempt to show a certain # of items (or you have items with large heights).
In reference to:
If I understand the problem correctly, in the past I've worked around this by having multiple "spacer" elements in the DOM which are of the maximum size. As long as no single element is bigger than the maximum height, this seems to work. So instead of setting the container element to 1,000,000 px (for example), you have multiple spacer children which are each 10,000 px for example. The spacer elements and the actual elements that are shown will together add up to 1,000,000 px. Hope that makes some sense!
IE also has the same issue btw (not sure about Edge).
The text was updated successfully, but these errors were encountered: