While these may not be blockers to using <datalist>, I think they're significant issues that should be considered, roughly in priority order:
1) Worst, <datalist> is always left-anchored, but our autosuggest is search-based with best-match ordering
2) We can't control the formatting of the display with CSS or HTML
2a) We lose highlighting, which was a big part of the original request, and helps to draw the user's eye based on overall matchiness and left-matchiness
2b) The class/field marker on the right is probably OK, because the text content of the <option> is displayed where we place it by default (though we can control it today with autosuggest)
(1) is the biggest problem, by far. It would significantly reduce usability of the feature, IMO.
While these may not be blockers to using <datalist>, I think they're significant issues that should be considered, roughly in priority order:
1) Worst, <datalist> is always left-anchored, but our autosuggest is search-based with best-match ordering
2) We can't control the formatting of the display with CSS or HTML
2a) We lose highlighting, which was a big part of the original request, and helps to draw the user's eye based on overall matchiness and left-matchiness
2b) The class/field marker on the right is probably OK, because the text content of the <option> is displayed where we place it by default (though we can control it today with autosuggest)
(1) is the biggest problem, by far. It would significantly reduce usability of the feature, IMO.