Streaming live at 10am (PST)

Dropdown OnHover not working on Chrome


#1

Heya!

This is a bit of a weird one. I have people experiencing problems with Webflow’s Dropdown element on the latest Chrome build - Version 64.0.3282.140 (Official Build) (64-bit).

I’ve set the dropdown to open On Hover, however for some people it doesn’t open on hover and they need to click the Dropdown Toggle to actually open the dropdown menu.

What’s even weirder is that I had two people test this on two different laptops, both of which running Windows 10 (64 bit) with the latest Chrome and for one of the users the dropdown worked on hover, while for the other it didn’t!

Weird, eh?

At first I thought the dropdown might be acting weird because of the styling and animation effects I added to it, but then I added a clean no-style dropdown element and it still wasn’t working. So I ruled that one out.

Can you please take a look into this? I think the problem might be in some of the JS you’re using to display the dropdown.

Thanks!


#2

Hi @Alex_Tokmakchiev I’m happy to look into this issue.

can you send me your site’s read-only link?


#3

Sure thing.
There ya go:
https://preview.webflow.com/preview/puzl-coworking?preview=0f703def2d536b814d1b87486633c3c2


#4

Hi @Alex_Tokmakchiev

Thanks so much for sharing that link. I did some testing on this end using your site. The dropdowns opened on hover as expected on Windows 10 + Chrome.

Can you provide a bit more information? Any screenshots / recordings you have of this behavior would be very helpful.

Can you also please try the following:
(1) Try to reproduce the error while being logged into Webflow using Incognito mode with browser extensions turned off: https://support.google.com/chrome/answer/95464?hl=en
(2) If the problem persists, please take a screenshot of your Console and send it to me: https://developer.chrome.com/devtools/docs/console

Thanks in advance!


#5

Hey @Brando,

Here’s a screenshot of the Console. This was taken on the Windows Surface, Windows 10 (64-Bit), Chrome (Latest build), where we first detected the problematic behavior.


#6

Thanks for sharing that screenshot @Alex_Tokmakchiev.

I’ll pass this info along to the team to see if we can uncover what’s going on here.

I’ll reach out with an update as soon as I can!

​Thanks in advance for your help and patience :smiley:


#8

@Alex_Tokmakchiev I wanted to share an update.

Our team was able to reproduce this behavior on Windows 10 + Chrome 64. We are currently looking into the issue to see if it’s something on our end or something on Chrome’s.

I will post back here with more information when I have it.

Thanks again for your help!


#9

Thanks, mate!

Appreciate you looking into it!