The field, by default, displays a prefix " https://www.drupal.org/u/ → ". This implies to the user that they need to fill in the username as displayed in the URL. However, the module actually invokes the API to get the user information and hence it needs the actual username. This creates confusion when username is different from the URL slug (for example, when there is a space in the username).
Try adding a username with space or other characters.
These are the options:
- Remove the prefix and accept a username.
- Keep the prefix and accept a space. This means we should first read the URL slug to find the user ID.
- Support both cases and give precedence to the actual username and then the URL slug if a user was not found. This could lead to confusion if not clearly communicated.
Decide which method to pick.
Active
2.0
Miscellaneous
As the description of the module says that it accepts the D.O usernames. I think our understanding of Drupal username is with the username field value that we have at /user/{uid}/edit page and it would be a good idea to use it instead of URL slug. I would vote to go with the first proposed option to 'Remove the prefix and accept a username'.