-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Remove enableLoader and built-in loading status management from lazy #3963
Comments
I have the same issue, but made a simple workaround by assinging a empty array to my datatable value. |
Hi thre xtoff ,could you mind explaining how? I have tried checking for the length to the variable that the datatable is looking for and tried setting it to |
@tapaccos In my loadLazy function (onLazyLoad), I set the value of my datatable [], the first time when this function is called. But in my case there is no data loaded on page load. Only when I click a search button. Maybe you should check if your value binded to your datatable is empty and set it [] in your lazy load function? |
Another solution would be to set lazy to false and use loading property instead. |
So when there is no data to load, change detection is not triggered so loading indicator is not turned off, I guess best solution is removing the built-in loading for lazy mode and let the page author manage it manually. |
I'm submitting a ... (check one with "x")
Current behavior
Current version of datatable will show the loading indicator if it's enabled and will hide the the loading indicator when some data is loaded/fetched by the
onLazyLoad
event, In some cases, if there is no data at all, the loading indicator will never be hidden.Under any situation, lazy loaded with no data is correct, but current design is no way to detect this. so when lazy load get no data at all, the loading indicator will never be hidden. In visual, this seems that the data load is never end, but the load process is correctly finished with just no data.
The text was updated successfully, but these errors were encountered: