1109177 - drupal administration dropdown menu display being cut off or absent

Status: RESOLVED INCOMPLETE

(Core :: Web Painting, defect)

Description

[Travis Butterfield]

To reproduce: Log into drupal site at (https://live-lodestar.ws.asu.edu/user) using username: firefox and password: firefox. The black admin menu bar will appear at the top of the page. Hover over an option in the menu that has a secondary option (indicated with a small arrow within a box at the right). 

Sometimes this secondary menu will appear, but sometimes not. When it appears, it becomes cut off prematurely. For example, when hovering over Content > Add Content, the options should be: Content callout box; Content page; and Landing page. Landing page does not display, but when you hover over the place where it should be, you can still click on it as if it had displayed properly. Another example is when you hover over Structure > Blocks, it should show: Add block; Add menu block; Kalatheme; and Seven. However, it is only showing the first two options.

Interestingly, when using the element inspector in Firefox Developer, the missing items will show up. But, they do not appear during normal browsing. I have tried to reproduce this bug on other computers, but it seems to have something to do with my local machine.

I have tested this on the latest Firefox Nightly version, and it still persists on my machine. I have uninstalled and reinstalled new Firefox browsers, and I have cleared all server and browser caches. Nothing seems to fix this problem, which leads me to believe it is a bug.

Comment 1

[Travis Butterfield]

Oops. I accidentally included the wrong URL in the description. It should be https://dev-travis-test.ws.asu.edu/user

Comment 2

[Ryan VanderMeulen [:RyanVM]]

The original URL is 404 now. Is there a site where this still reproduces?

Comment 3

[Mike Gifford]

Generally it's best to spin up a new instance to verify that it's actually just Core that is causing this problem:
https://simplytest.me/project/drupal/7.x

Also, quite possibly this is a Drupal issue. There should at least be an issue queue on Drupal.org about this.  

Quite likely it's something tied to this implementation.  This is an old issue, probably should be closed.

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Closing this based on the lack of actionable information to move forward here. Feel free to reopen if new steps to reproduce or (better yet) there's a testcase that readily reproduces the problem still.