Fast Permissions Administration and D8 and core

#1475204: [META] Provide a generic search/filter UI interface pattern for listing pages
#1757618: Add Instant filter functionality in D8 core.
#1279652: Add title search feature on the node listing admin page

I just downloaded and checked out how D8 is doing the incremental filter on the modules page.

It currently iterates over each row checking for a match in the row's text.

This works well for a small number of rows, but quickly becomes unusable when you have a large number, such as the permissions page. You can easily have a 1000+ permissions on a Drupal website that have numerous content types and modules installed.

FPA sidesteps the issue and offloads the decision of which rows to hide to the browsers CSS engine, by dynamically generating CSS that is injected to the page and hiding rows based on attributes that are attached to them. I'm not sure if there is a faster method than letting the CSS engine hide and display the rows.

An example with a large number of rows can be seen here http://www.m29.com/fpademo/index.1k.html.

One draw back is that FPA must prepare the rows since they do not have these attributes by default. This does add a little overhead at the start, but the initial small wait generates much less frustration down the line with the faster filtering.

In #1938938: Convert theme_user_admin_permissions() to table #type since we are converting the form to a #type => 'table' we could also add row attributes of the text that we want to filter on. This would remove the preparation step that is required for using a dynamic CSS based solution and allow for a very fast filter without any apparent initial overhead.

This technique should work in IE7+ and all other mainstream browsers.

If we do this for the permissions page, would we want to instead provide a more generic JS library that can be used anywhere a #type => 'table' is displayed? This would help to reduce the amount of similar functionality that sprinkled around a D8 install.

Drupal 7 is no longer supported.
Issue is older than 8 years old.
Closing as outdated.