4 ms·

I don't know about the 2008 stuff but I found the site to be pretty broken, as in things clearly not working and the code blowing up. The design is very busy on

I don't know about the 2008 stuff but I found the site to be pretty broken, as in things clearly not working and the code blowing up. The design is very busy on desktop; I suspect your "clean design" is what you see on mobile. The desktop site is packed to the gills and every page has multiple things animating and bouncing at me. Let me make it clear--this site is busier than most, not cleaner. On desktop, it's pretty easy to open one of the menus on the top and then have it fail to close. Since the site disables the scrollbars while a menu is open, it breaks the site until you figure out the magic spot to move the mouse to make the menu close again. The magic spot doesn't seem to be in the same place every time. Seems buggy. I spent most of my time on this site with one of the menus open, unable to scroll down and see beyond the first page. The worst part? The links in the menus don't work. A peek in the source code suggests they are supposed to be links, but clicking them doesn't do anything because they're just <div>s (not real <a> links) and the click event handler simply calls preventDefault (QTools.js line 107). That finicky navbar nearly ruins the entire site. I'm almost entirely unable to navigate around. This site is, unfortunately, pretty broken on desktop Chrome. Test your site on desktop in addition to mobile. I got the site to hit an explicit debugger breakpoint in Q.js line 10293 just by clicking around the top menu buttons. The author of that code didn't bother writing an exception handler, they just had it trigger the debugger. I do find it offputting; the site definitely has the feel of "a programmer hacked this together without any input from a designer." The massive drop shadow from the embedded videos actually covers up some of the text on desktop. The font is VERY thin--make sure to check your site on Windows and not just macOS. More generally: hire a designer. Programmer designs stick out in a bad way, and users seeing a broken marketing site will assume the product is broken, too. I certainly do.

EGreg 3y ago
I want to fix what you're talking about, but I was not able to reproduce the bug. Can you please tell me how you got the menu to not close, for instance? Also, clicking on the menu items clearly opens the page they're linked to. I couldn't get it to not do that.
- 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 ago
    Tried 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 ago
      I'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.

EGreg 3y ago

I want to fix what you're talking about, but I was not able to reproduce the bug. Can you please tell me how you got the menu to not close, for instance? Also, clicking on the menu items clearly opens the page they're linked to. I couldn't get it to not do that.

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 ago
  Tried 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 ago
    I'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.