Opened 7 years ago
Closed 5 years ago
#44035 closed defect (bug) (invalid)
Admin flyout submenu does not open on mouseover when changing device width in browser
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Menus | Keywords: | reporter-feedback |
Focuses: | administration | Cc: |
Description
On Chrome (Version 66.0.3359.139 (Official Build) (64-bit)), if I switch to mobile view from desktop, refresh the page and then switch back to dekstop view, no flyout submenu is opening on mouseover.
For example, if I hover on Posts
menu, the flyout menu is supposed to appear but it is only appearing when I click on it! Which also means the click event does not take me to the posts list page immediately. Once I click on All Posts
link, everything gets back to normal.
OS: Ubuntu 14.04
Steps to reproduce:
- Go to admin.
- Press Shift+Ctrl+I to reduce viewport size.
- Refresh the page.
- Press Shift+Ctrl+I again to go back to desktop view.
- Mouseover on Post or Pages or Appearance. Flyout menu will not appear.
- Click on the menu item to bring up the Flyout menu.
Change History (4)
This ticket was mentioned in Slack in #accessibility by afercia. View the logs.
7 years ago
#2
@
7 years ago
- Focuses accessibility removed
- Keywords reporter-feedback added; needs-patch removed
#3
@
7 years ago
@afercia Sure! I would try that and get back to you with my findings.
Thank you for looking into the ticket.
#4
@
5 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
@subrataemfluence this makes sense to me as when in mobile, there is no ability to hover. So loading the page in mobile won't register the hover events so they won't be available when in desktop mode.
Removing the accessibility focus since this happens for all users, not strictly related to a11y issues.
@subrataemfluence could you please try it with the Chrome inspector responsive view emulation set to "desktop"? I think it happens only when set to "mobile" so switching form "desktop" to "mobile" produces this issue.
Instead, when using normally a device, it's either a "mobile" or "desktop" device, so I'd recommend to test on real devices.