Table rows should be able to scroll down independently

[Praveen Kumar SM]

We can not scroll down just table rows. We can only scroll the whole web browser page.
If the user has scrolled down the page and wants to click different system panel then he has to go back to the top of the browser and then click on different system panel. This is usability issue when the number of rows are high.

Example:
Consider 1000 entries are there in the Networks table and user wants to delete network at row number 500. In this case he has to scroll down to 500th row entry and select the row and then once again come back to the top of the browser and press delete button.

Here table and other configuration panels needs to be organized in different UI panels.

[Liz Blanchard (lblanchard)]

I wonder if a good search and pagination combo solution would work in this case. The user would be able to filter down the list of networks in the table to find the network that they wish to delete. They can quickly select to delete that network without even having to scroll the page at all.

[Cindy Lu (clu-m)]

Nice scenario to illustrate the problem, Praveen.

Agree with Liz. Filter+pagination seems to be the right approach. However, Horizon is dependent on API support across the projects, which is inconsistent right now.

[Praveen Kumar SM (praveen-sm-kumar)]

I also agree with Liz.

[Timur Sufiev (tsufiev-x)]

Closing this feature request as Won't Fix because showing such a big amount of objects will slow down Horizon considerable, so Pagination + Filtering is indeed the proper solution for this problem.