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
Was just wondering about this component, when used on page with lots of things to observe, like an image gallery of similar, it would create am InteractionObserver for each usage instead of reusing a single observer.
Do you know if this would matter that much to performance or so ?
Perhaps if the observer options are the same, it could reuse it for multiple elements ?
The text was updated successfully, but these errors were encountered:
@bobmoff, Yeah you're absolutely right. We might be better of having some sort of factory which creates Observes based on the configuration settings. This does however require some rewriting of the codebase and additional tests, but i think it's absolutely doable.
In my experience there is no direct performance implications when having multiple observes, but that of cause depends on the amount of observable elements that one might have.
Hi!
Was just wondering about this component, when used on page with lots of things to observe, like an image gallery of similar, it would create am InteractionObserver for each usage instead of reusing a single observer.
Do you know if this would matter that much to performance or so ?
Perhaps if the observer options are the same, it could reuse it for multiple elements ?
The text was updated successfully, but these errors were encountered: