a.f.a.i.k, that's what dropdown tags is for ?  If you agree, I would propose to remove this idea.

Or is there stuff dd search can do, that dd tags can't ?

@Dorine Boudry, that's a valid point, and the Dropdown Tags widget gets us halfway there. However, our use case includes users that are differently abled and have to use the keyboard to navigate the page, and the tags are not individually selectable nor are the selected items configurable to place at the top of the list. 

I mentioned keyboard navigation at the end of my original post, but I should have been more clear at the top what I meant when I said 'click'. We're just trying to avoid a situation where users who cannot use a mouse can still delete selected items without having to scroll to find them again or delete all of them to start over.

Ok, that last half sentence didn't register with me.

There is an option to show the selected ones at the top though, just use the client action SetVirtualSelectConfigs in the Initialized event of the widget.

It is available on both dropdown tags and dropdown search (same underlying library)

so my questions is again, can we close this idea as already implemented ?

@Dorine Boudry, good point the virtual select configuration options. I've used them before when specifying the aria-labels, though I didn't realize they also had that option as well. That should work for what our developers need. I think we can close this one.