9 ms·
Reproduction steps: 1. Install Chrome for Windows from the Google website. As of today, that version is 114.0.5735.199 (Official Build) (64-bit). I am testing
by electroly 3y ago
Reproduction steps:
1. Install Chrome for Windows from the Google website. As of today, that version is 114.0.5735.199 (Official Build) (64-bit). I am testing on Windows 11 and I used a fresh install of Chrome on a machine that has never had Chrome before. This machine has a standard 60Hz display which may matter for my theory at the end.
2. Go to qbix.com.
3. Hover the mouse over "Communities". Now hover over its submenu items. Observe that they do not highlight on rollover like they're supposed to, and clicking on them does not do anything.
4. Now quickly move the mouse outside of the menu. Observe that the mouse escapes the menu, and the menu does not close. Move the mouse around the rest of the page. Observe that the menu continues to stay open. Observe that you can't scroll the page. In this state, the site is unusable.
5. Move the mouse back inside the menu, then slowly move the mouse across the edge of the menu. Observe that now the menu closes.
I have reproduced the same in Edge and Vivaldi; the issues appear to manifest in Chromium-based browsers on Windows. I tested on macOS and iOS and the issue does not show up there. I can provide a screen capture if needed. Without looking deeper, I wonder if this page is trying to use JavaScript to close the menu based on a mouse event that it misses when you move the mouse too fast. I wonder if the entire navbar is implemented in JavaScript instead of a modern CSS-only technique with regular links.
- EGreg 3y agoTried it with Chrome and Edge on Windows. Still can't reproduce those bugs. Strange. The worst thing is when some users see a heisenbug that you can't seem to reproduce on a similar environment.
- electroly 3y agoI've tried it again on both Windows 10 and Windows Server 2022 and it reproduces every time. I have yet to see the site working properly on Windows Chromium. Please try creating a fresh cloud Windows instance rather than using your usual computer so you can be sure you are seeing what a fresh user on a new computer would see. I have done so--this reproduces in the preinstalled Edge on a brand new c6a.large Windows Server 2022 instance in AWS. I can provide a click-by-click screen capture starting at the AWS Management Console if desired--I've found this is a good way to prove bug reports to companies and demonstrate that it has nothing to do with my computer.
- electroly 3y agohttps://youtu.be/NTujUB8t4tE https://youtu.be/NTujUB8t4tE Here is the screen capture. This video shows the creation of a fresh Windows instance in AWS EC2 and then the reproduction of all of the above issues in that fresh instance. Follow my exact clicks and you will see it, too.