3 ms·
No, it's because Twitter Web removes elements from the DOM when they are far from the viewport. There are two ways you can see it: 1. Open a DOM debugger, sel
by progval 6y ago
No, it's because Twitter Web removes elements from the DOM when they are far from the viewport.
There are two ways you can see it:
1. Open a DOM debugger, select an element in a tweet, scroll down. Eventually the element disappears.
2. In Firefox, scroll down, right click, "Take a screenshot", "Complete page". You'll see tweet far from the viewport, as well as header and sidebars are invisible.
The motivation is probably to make it faster, but it's unclear to me why removing (and later re-adding) elements in Javascript would be more efficient than the browser internally dealing with it.