If you hover with a mouse pointer, over where autocomplete suggestions will show up, and then type; the autocomplete suggestion will become a link (or at least visually become underlined, and therefore look like a link).
This is extremely minor, however when it first happened to me, it seemed a bit confusing. I thought I'd mention it anyway for the sake of completeness.
Note for Windows users: The attached video is QuickTime (.mov), however it also plays in VLC for people who don't want to download QuickTime for Windows. I didn't have a converter, so apologies for any inconvenience playing the video.
Comment | File | Size | Author |
---|---|---|---|
Autocomplete Link When Hovering Cursor.mov | 741.29 KB | CatsFromStonehenge |
Comments
Comment #5
driverok CreditAttribution: driverok at EPAM Systems commentedComment #6
driverok CreditAttribution: driverok at EPAM Systems commentedComment #8
anschultz CreditAttribution: anschultz commentedWe looked at this issue during DrupalCon 2019.
We discovered that the behavior is due to focus vs hover styling. Technically your mouse is still hovering on the element, even if the focus changes. You can also reproduce the bug if you hover over one autocomplete option, and use the keyboard arrow keys to switch focus to other elements.
We think a solution would be to turn off the hover pseudo-class for the autocomplete elements. Something like $('#elementName').off('hover')
We were unsure where to place a solution like this. We looked at /core/modules/field_ui/field_ui.js as a possibility, and ran into the js contributer workflow (https://www.drupal.org/node/2815083).
This may seem like a small issue, but it seems like a can of worms. We discussed if philosophically keeping the hover would be correct (technically the user is still hovering on the element), but looking at the amazon.com dropdowns, they don't have the issue of hover vs focus styling (and we know they've spent a lot of money on UX development).
Comment #16
LendudeThank you for reporting this and the analysis in #8.
I tried to reproduce this following the steps in the IS and the provided movie. Using a clean Umami install on OSX using Chrome in the Claro theme, I could not reproduce this any more.
Is this still an issue for somebody? Is this OS/Browser/theme specific maybe? Or does this seem to be solved?
Comment #17
bnjmnmI could not reproduce this with any of the current core themes (Claro, Olivero, Stark, Umami).
The video provided in the issue summary suggests this is not a Drupal core issue
This is something that can be addressed if we're provided steps to reproduce on a site that uses only themes + modules provided by Drupal core.
Comment #19
quietone CreditAttribution: quietone as a volunteer commented@CatsFromStonehenge Thank you for reporting this problem. We rely on issue reports like this one to resolve bugs and improve Drupal core.
There has been no activity here for N years M months.
More information about this issue was asked for 12 months ago and then 9 months. No additional information has been supplied. Since we need more information to move forward with this issue and it is has not been supplied I am closing this.
If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue (starting from "Install Drupal core").
Than