-
Notifications
You must be signed in to change notification settings - Fork 107
Not destroying invisible list elements when using without ui-scroll-viewport #78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you post a repro for your problem? Michael Feingold, President On Sat, Apr 2, 2016 at 1:31 PM, moosi [email protected] wrote:
|
Thank you for your fast response. I created a demo for you: |
+1 |
It defenetly can be reproduced on our Entire window scrollable demo. And the bad news is that this demo does not work for a long time. As I remember about 20 days ago we did some fix related to this demo (cause it was totally broken) but we did not check removing from DOM after this... Thanks @moosi. I see that during scrolling down every item in the buffer has positive We need to take care of this. |
I solved the issue by clipTop/clipBottom refactoring. Now these pieces of logic are really unified and transparent. The code is in master and will be included in 1.4.1 release soon. |
Thank you so much for the fast implementation! First tests were successful :) |
Fixed in v1.4.1. |
I am currently facing the problem that ui-scroll is not working as expected if I don't use a fixed height with ui-scroll-viewport.
I am using the plugin for different feeds in my app. For example:
--- Top Nav ---
--- Feed ---
--- Bottom Nav ---
or
--- Top Nav ---
--- User Profile ---
--- User Feed ---
--- Bottom Nav ---
Because of this setup I need a dynamic list height. After removing ui-scroll-viewport my posts are loaded as expected when I scroll down but the DOM is growing and growing without destorying the invisible elements.
I am using version 1.3.3 with angular 1.3.2. Is there any solution for my problem?
The text was updated successfully, but these errors were encountered: