Autocomplete has the option to disable search for certain input using the attribute data-autocomplete-first-character-blacklist on the autocomplete form element. Unfortunately this doesn't stop EntityAutocomplete::validateEntityAutocomplete() to search for strings matching the blacklist or trying to validate these strings.
I stumbled across this while working on
#2756247: UX improvement: use autocomplete for entity selection in area handlers →
.
EntityAutocomplete::validateEntityAutocomplete() does not search for strings matched by the configured blacklist and does not try to validate these strings.
Convert to MR
Do not add new uses of the word 'blacklist', see
#2993575: [meta] Remove usage of "blacklist", "whitelist", use better terms instead →
Add tests
None.
None.
None.
Needs work
11.0 🔥
It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Seems this was tagged for additional test scenarios in #37
Updated the issue summary. The first two tasks are suitable for a novice.