This is a lazy, and bad way to implement it. Continually adding stuff to the bottom of the page for an 'infinite' scroll is a sure-fire way to slow the browser down and eat memory. You should also remove items from the top that have scrolled out of view, and readjust accordingly
I totally agree that not removing the items from the top that have scrolled out of view eats away at the memory, but its not feasible in most use cases, especially where the data is dynamic like Facebook (FB doesn't implement this feature either).
This is a lazy, and bad way to implement it. Continually adding stuff to the bottom of the page for an 'infinite' scroll is a sure-fire way to slow the browser down and eat memory. You should also remove items from the top that have scrolled out of view, and readjust accordingly
I totally agree that not removing the items from the top that have scrolled out of view eats away at the memory, but its not feasible in most use cases, especially where the data is dynamic like Facebook (FB doesn't implement this feature either).
Yes it does.
1 page on Facebook:
10 pages on Facebook:
