Opened 13 years ago
Closed 12 years ago
#19562 closed defect (bug) (fixed)
Admin menu positioned incorrectly
Reported by: | phill_brown | Owned by: | koopersmith |
---|---|---|---|
Milestone: | 3.4.1 | Priority: | normal |
Severity: | normal | Version: | 3.3 |
Component: | Administration | Keywords: | has-patch commit |
Focuses: | Cc: |
Description
The WordPress menu positions incorrectly in a scenario where it's collapsed, hovered and then expanded again.
- Select a menu item (easiest to use Settings)
- Collapse the menu
- Make the height of the window small enough so the sub-menu is forced to move up the page on hover ie the menu won't be inline with it's original hidden position.
- Expand the menu
I've attached two screenshots to better explain the issue and a patch that fixes it.
An alternative fix would be to traverse each sub-menu when the collapse link is clicked and remove the top margins.
Attachments (4)
Change History (16)
#1
@
13 years ago
- Summary changed from WordPress admin menu positioned incorrectly to Admin menu positioned incorrectly
#4
@
12 years ago
- Keywords reporter-feedback removed
Still seem to be able to produce it on the latest in SVN...
#5
@
12 years ago
Following the exact steps from the ticket, can't reproduce it. When the menu is expanded any positioning from any sub-menus is removed: http://core.trac.wordpress.org/browser/trunk/wp-admin/js/common.dev.js#L175
#6
@
12 years ago
Ah hang on, my mistake sorry. The error now only occurs when the navigation menu collapses and expands automatically when the browser window resizes. Try this:
- Select 'settings'
- Maximise your window with the menu in it's default expanded state
- Shrink your window so it's small enough to trigger the collapse state.
- Scroll down the page so the position the settings icon is near the bottom of the window.
- Hover over the settings icon. The positioning of the window should force the sub-menu heading out of line of the icon ie the menu won't be inline with it's original hidden position. See mouseon.jpg.
- Maximise the window again so the menu expands. This should produce the broken state similar to that shown in expanded.jpg
Just checked my patch and that still appears to fix the problem. It looks like this ticket was in part duplicated and fixed in ticket 20857.
#7
@
12 years ago
- Keywords has-patch added
- Milestone changed from Awaiting Review to 3.4.1
I can reproduce it with the steps from the latest comment.
Refreshed the patch to reset margin-top
, like we do in lines 176 and 213.
#8
@
12 years ago
I can reproduce it too. Maybe we don't need both removals of the sub-menu negative margin, but as far as I remember sometimes mouseleave doesn't fire right.
I think this is no longer reproducible in 3.4.