Search filter-lists by content

[Rudxain]

As of v1.59, the search-box in the "Filter lists" tab can only search filter list by name (erratum).

I propose 2 options:

• Remove the search-box: This will make development easier for maintainers, and will free up screen and storage space.
• Allow searching the contents of filter-lists, as if the asset viewer was open for every file (is this "recursive"?)

For content search, it doesn't have to be "advanced" with highlighting or anything, just show the lists that contain the sub-string

[Rudxain]

already solved by implementing in uBO a "Troubleshooting" tab

I agree. For that use-case, the tab is much better.

[1]

IMO: +1% convenience. +8% "noise" reduction.

[2]

IMO: +2% convenience.

[3]

+8% convenience. ~ -5% performance? (unsure)

Final (personal) score: +11% convenience, +8% focus, ~ -5% perf. Not bad.

I believe other users will find it more useful, so the feature should stay. You've convinced me!

limit your search to titles only

I'm sometimes afraid of doing that, then not finding what I'm looking for. But the strategy of doing a narrow-search followed by a broad-search might be helpful sometimes. Thanks for the suggestion 👍

[Rudxain]

sarcasm

I genuinely believe the feature is useful for some users, but (for me) it's not so helpful :/ . I don't even use the browser's built-in search often, as the "Filter lists" tab isn't long, and I rarely visit it. I'm mostly concerned about my Dyn-Rules, where the search-box is very helpful, as it searches the contents of a "big" list.

providing some % based calculations, which noone have clue about how they were calculated (except you)

I'm not even sure how I calculated either 😅. Roughly: 0% = "absolutely no diff", +25% = "noticeably better than no search-box", +50% = "considerably better than no search-box", +100% = "2x better than no search-box" (1 binary order of magnitude). But even those terms are vague and subjective, so I'm not sure how to properly measure or communicate them 😕

There is a about 0,5-1 second delay after searching using Chromium search box before results appear, which might be annoying: Chromium video. In uBO search box, results are instant after typing every letter (I guess perhaps 50ms-100ms): uBO video

I meant "perf of not searching anything" (always negative for any search implementation). But it makes more sense to measure WRT the browser search, as it's more fair. In this case it's between ~10% and ~0%

[Rudxain]

The toggle seems like a nice middle-ground. I like that idea

[Rudxain]

I've searched "annoyance", and the results show:

• "Cookie notices"
• "Social widgets"
• "Annoyances"

This obviously implies the search-box does more than just match titles