// Don't forward if no relevant infomation changed
if (!info.changed) {
return false;
}Updating from 1.x to 2.x I noticed this, which kinda ruined a use case of mine. I basically have a growing list with a spinner at the end. When the spinner is visible, the content is rendered but the spinner element is kept for further growing the list when the user scrolls some more.
Problem: if the initial value of the list sub-set is small, the spinner is immediately seen and more data rendered. If the spinner is still visible (big screens), nothing happens because effectively nothing changed in terms of visibility, but I want the callback to be called anyway.
Could you consider making this optional? I can make a PR if you agree. Thanks!
Updating from 1.x to 2.x I noticed this, which kinda ruined a use case of mine. I basically have a growing list with a spinner at the end. When the spinner is visible, the content is rendered but the spinner element is kept for further growing the list when the user scrolls some more.
Problem: if the initial value of the list sub-set is small, the spinner is immediately seen and more data rendered. If the spinner is still visible (big screens), nothing happens because effectively nothing changed in terms of visibility, but I want the callback to be called anyway.
Could you consider making this optional? I can make a PR if you agree. Thanks!