if the parameter layout="table" is passed, the component behaves with undocumented features.
When typing in the input a selection list is displayed. Mouse over the selection list and the wrong selection is displayed in the input.
This problem can be recreated in the show case by simply added the layout=”table” parameter to and existing autocomplete component.
Though in the showcase there is limited selections, if a larger listed is added you can see that the first highlighted row maps to the correct selection +1... the second highlighted row maps to the correct selection to +2 ..etc.. so it appears there is an iterator off somewhere.