Xon
Xon
That sort of pagination/scrolling would require a fairly significant architectural change to the rendering code, so it isn't going to be something done in a hurry.
The `renderSelectedChoices` option doesn't apply to search, but it shouldn't be hard to add change this.
> also [@Xon](https://github.com/Xon) the appendGroupInSearch: true is not working on v11 This will be fixed in the next version. When I have some more time I'll work on a better...
The failing e2e test is from a random browser update and now some icons render differently, that can be ignored
I've been meaning to finish off some bugfix work but haven't had a chance due to other projects. I'll try get a 11.2 build out next week
There currently isn't any event for an item/choice click
@MarkoSh you will want to use `choices._store.choices` not `choices._currentstate.choices` for compatibility with `v11.0.0`. I've prototyped up an `Choices.updateLabel` command but I'm still working on finishing off `v11.0.0`, with a primary...
The search feature doesn't actually use the `data-custom-properties` attribute on the rendered choices list. It loads them from the backing ``'s and persists that as part of it's internal representation....
@samuelhwilliams I plan to merge #1357 first, but it looks like your change has some stray changes in the built assets. It may be easier to just revert changes to...
This does introduce a behavior change with the default of `auto` instead of `false`