When I click the "hamburger menu" in the right part of the top bar:

I usually get the site switcher drop-down:

site switcher drop-down

But sometimes, I'm taken to https://stackexchange.com/ instead:


It isn't very consistent. I tend to get the drop-down if the page has been loaded for more than a few seconds. I most often get the SE homepage if I click in the first couple seconds after the page loads, although sometimes I get the drop-down even if I click very quickly.

But it doesn't always seem to happen. When I started writing this question I had no trouble getting it to occur, five minutes later I couldn't reproduce it, and ten minutes later I could again. At the moment my guess is that it's related to how quickly some page element loads.

Being unable to predict the results of clicking the top-bar is somewhat confusing, although it does work most of the time, so it's not terribly frustrating.

It took me a while to figure out that it wasn't my own fault—at first I thought that the "StackExchange" text linked to SE and the down arrow showed the drop down, and that the inconsistency was a result of my inaccurate clicks. Doing some experimentation, it seems that this is not the case, and the entire rectangle (circled above in red) has the same behavior.

I've observed this behavior in SeaMonkey 2.26 and Firefox 28, and Nick Stauner has reproduced the problem in Chrome 34 (see comment below).

  • 4
    Repro'd right away and consistently in Chrome 34 by just refreshing the page with my cursor in position over the Stack Exchange™ MultiCollider SuperDropdown™, ready to click frantically as soon as I'd hit F5. I remember noticing this before too BTW...always assumed it was a misclick on my part too. Wonder if it has something to do with the positioning of the Stack Exchange link at the top of the list before its frame structure loads (pardon my lack of correct jargon)...Maybe the link object appears superimposed at first and then drops down once it's fully loaded? – Nick Stauner May 7 '14 at 7:12
  • 1
    The return of this old bug. – Shadow The Vaccinated Wizard May 7 '14 at 8:42
  • 1
    I always see this behavior on mobile if the page hasn't loaded fully. – brasofilo May 7 '14 at 10:34
  • 1
    This happens to me a lot (Firefox) and is very annoying. It's two clicks to get to a different site's meta (assuming the main is on my list), so if that's my destination I tend to make that second click pretty quickly -- and am foiled about half the time. It's been like this for a couple weeks. – Monica Cellio May 7 '14 at 18:27

The ideal behavior of the top bar buttons should satisfy the following goals:

  1. When clicked normally, in a browser that supports JavaScript, they should open/close the menu.

  2. If the menu cannot be opened yet, because the necessary scripts have not yet loaded, the button should either do nothing, or the menu opening should be deferred until it can be done.

  3. If JavaScript is not supported or enabled, the buttons should default to working like normal links.

  4. In any case, middle-clicking the buttons should always act as if they were normal links, opening the target page in a new tab.

The current implementation, which defines the buttons as normal links in the HTML, and then later adds a jQuery event handler to catch normal mouse clicks and toggle the menu, meets all these goals except #2.* The reason it doesn't meet that goal is because it takes as while for jQuery and the SE framework to load, and until then, the buttons act like normal links.

There are several ways in which this could be fixed without compromising the other goals:

  • The buttons could be marked in the HTML with old-style onclick handlers that stopped them from working as normal links (and, optionally, recorded the clicks for deferred execution) until the jQuery code loads, at which point these handlers could be removed and replaced by the real menu toggling handler.

  • Alternatively, some in-line JavaScript code, embedded in the HTML immediately after the buttons, could inject temporary event handlers that achieve the same purpose. This might leave a small window of vulnerability between the loading of the buttons and the execution of the code, but it should at least significantly reduce the problem.

  • Even better, some inline JavaScript, embedded in the HTML before the buttons, could add a click event handler on one of their parent elements (such as the .topbar div) that detected clicks targeting the buttons and disabled their normal operation. Conveniently, this handler would not even need to be removed later, since the real menu toggle handlers would pre-empt it.

The next version of the SOUP user script will include a client-side implementation of the last option above (assuming that this bug isn't fixed before its release). Adventurous users can grab the pre-release development version from the GitHub repo here. For the merely curious, here's what the code looks like:

var buttonRegex = /(^|\s)js-(site-switcher|inbox|achievements|help)-button(\s|$)/;
document.addEventListener( 'click', function (event) {
    if ( event.button != 0 ) return;  // ignore right/middle clicks
    var elem = event.target;
    while ( elem && !buttonRegex.test(elem.className) ) elem = elem.parentNode;
    if ( elem ) event.preventDefault();
}, false );

(The event handler is set on the root document object, because at the time the user script runs, there's no guarantee that any other part of the DOM is present yet. In a proper SE-side fix, the handler could be installed on a closer parent element of the buttons.)

* Well, in Firefox it does, at least. In Chrome, middle-clicking seems to also toggle the menu, which is probably a bug, or at least a misfeature (being neither expected nor useful behavior, for users used to middle-clicks opening a new tab). It does seem to be a different bug from this one, though. Also, currently only the site switcher menu actually has a useful middle-click / no-JS behavior; the others just have href="#".

You must log in to answer this question.