FIX various bugs on Autocomplete component

[gmercey]

Fixes

• https://github.com/buefy/buefy/issues/4098
• https://github.com/buefy/buefy/issues/4130
• Autocomplete selection and dropdown logic

Improvements

• recompute whitelist dynamically
• update ariaAutocomplete when keepFirst changes
• adjust scroll listener when appending to body
• test Autocomplete for 0 values, clearOnSelect, whitelist updates, etc.

[netlify[bot]]

✅ Deploy Preview for buefy-org ready!

Name	Link
🔨 Latest commit	bdbab349fccf34f1a0c6dc9b790ad557ad62cf27
🔍 Latest deploy log	https://app.netlify.com/projects/buefy-org/deploys/685ad3f3d9be370008044c94
😎 Deploy Preview	https://deploy-preview-4139--buefy-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[dagnelies]

This seems to break key navigation with normal async data

[gmercey]

This seems to break key navigation with normal async data

how did you get the broken behavior? I tested the component manually and the key navigation works in all cases.

[dagnelies]

Here: https://deploy-preview-4139--buefy-org.netlify.app/documentation/autocomplete#async-with-custom-template

I can only navigate the two first elements with the up/down keys... depending on what I type it the search. Sometimes it works, sometimes not, which is really fishy. It looks like long lists are more likely to be buggy. The same happens with both async demos.

[gmercey]

looks like the buggy behavior is happening when infinite-scroll is on ?

[gmercey]

Here: https://deploy-preview-4139--buefy-org.netlify.app/documentation/autocomplete#async-with-custom-template

I can only navigate the two first elements with the up/down keys... depending on what I type it the search. Sometimes it works, sometimes not, which is really fishy. It looks like long lists are more likely to be buggy. The same happens with both async demos.

Though one to debug, but here's an update