This won't work if collapse: false, so you could use a custom class (via the class parameter).

@FelipeRearden Try this and see if it works for your case:

Thanks for the snippet Chris! Unfortunately, it has one tiny detail that changes the main idea:

Let me explain the idea: when we have allowCustomInput = true we have 2 color changes:

Color 1️⃣ Prompt-input is empty (:placeholder-show) -> color black
Color 1️⃣ Prompt-input has one item from the list ["dog", "cat", "cow"] -> colorblack`

Color 2️⃣ Prompt-input has something that is NOT in the list duck -> colorgreen`

As you can see from below green appears when I type dog and duck. The idea is to show green only when I type duck

I really don’t know if this idea is feasible, because I dont know if you can target the duck suggestion-item alone

This won't work if collapse: false, so you could use a custom class (via the class parameter).

Same behavior on my end when collapse: true

this native obsidian suggester Open quick switcher command shows a representation of my idea:

• it has a visual UI that the input from the user is NOT on the list that the user is interacting with.

That’s what I think would be great for allowCustumInput !

Thank you very very very much for the new release Chris!

I think I found something wrong, but could be on my end. Let em check some things with you….

Same example:

const values = ["dog", "cat", "cow"];
const keys = ["dog", "cat", "cow"];
const selectedKey = await ntb.suggester(values, keys, {
icon: "vegan",
allowCustomInput: true,
placeholder: "Select a note..."
});

My question is about the existence/presence of .suggestion-item.is-selected.ntb-is-custom-input in these scenarios:
1️⃣ Prompt-input is empty
2️⃣ Prompt-input has one item from the list ["dog", "cat", "cow"] -> dog
3️⃣ Prompt-input has something that is NOT in the list -> duck

✅ 1️⃣ Prompt-input is empty -> there is NO .suggestion-item.is-selected.ntb-is-custom-input

Lets see the console for 2️⃣ and 3️⃣

📸3️⃣

📸2️⃣

QUESTION: should we dont have .suggestion-item.is-selected.ntb-is-custom-input since dog is on the list?

Based on my poor knowledge the snippet will trigger green when we are have dog as well because we have .suggestion-item.is-selected.ntb-is-custom-input

Can you reproduce this on your end? Maybe is related to my old obsidian version. Something tells that is working on your end

Let me know if you need more info 🙏

@FelipeRearden Ahh, sorry about that. Let me dig in to that.

@FelipeRearden So sorry, it's been fixed now. I didn't test this feature as well as I should have, so thanks for that! 😅

I've replaced the release with a new one. Please give it another try when you get a chance. (It shouldn't have anything to do with your "old" version; it doesn't depend on the Insider release for anything.)

@FelipeRearden So sorry, it's been fixed now. I've replaced the release with a new one. Please give it another try when you get a chance.

Working perfect on version 1.29.24 thank you very much for the quick fix ☀️

(It shouldn't have anything to do with your "old" version; it doesn't depend on the Insider release for anything.)

Great to know Chris!!!

I didn't test this feature as well as I should have, so thanks for that! 😅

No problemn at all Chris! That’s why I am here to as a tester, to add another layer of operation for the feature before the NTB community start using :)

Thanks again and I wish you a fantastic day ☀️