Search function sometimes doesn't work as intended to be for some nodes

[kayselmecnun]

I'm facing this problem every time I use the "SDXL Empty Latent Size Picker" node.

Typing "latent s" brings the node, while typing any other letter returns no results such as "latent sdxl", "empty latent", "sdxl latent"

[kayselmecnun]

Update: With the latest v1.1.9, the search function works a bit differently. It doesn't act like the previous version and shows results. But the search function still doesn't act normally. See the examples below; The Goal is accessing the "SDXL Empty Latent Size Picker" node, when I type "SDXL Empty" it brings the correct node on top, but when I type "SDXL Laten", it brings unrelated results with my keywords on the top, and the node I'm looking is placed 8 scrolling below.

[huchenlei]

The search impl comes from https://www.fusejs.io/. As far as I know it just performs string distance based fuzzy search, i.e. how many operations is required to convert one string to another. So SDXL Latent gets you Empty"SD3Latent"Image is expected.

I am not sure if we need to use a more powerful search provider if later we expand the search range to all sorts of things.

[huchenlei]

BTW, the theme of search box seem to be wrong. Can you share your browser console log, and screenshot? The searchbox theme should follow your ComfyUI theme.

[christian-byrne]

The field length norm might be too high. After using it a while, it does seem to give a lot lower weight to longer names

[huchenlei]

You can tune the fuse search params to try get better experience. It does offer option to weight down or disable field norm / location.

    this.nodeFuseSearch = new FuseSearch(data, {
      keys: ["display_name"],
      includeScore: true,
      threshold: 0.6,
      shouldSort: true,
      ignoreFieldNorm: true,
      ignoreLocation: true,
    });

[kayselmecnun]

BTW, the theme of search box seem to be wrong. Can you share your browser console log, and screenshot? The searchbox theme should follow your ComfyUI theme.

127.0.0.1-1721639801108.log

[SirVeggie]

The current search functionality should fix this issue, so this can probably be closed.