WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#8612 closed enhancement (wontfix)

Menu expansion on hover

Reported by: g0wda Owned by: g0wda
Milestone: Priority: normal
Severity: normal Version: 2.7
Component: Administration Keywords: has-patch
Focuses: Cc:

Description

You can reduce the number of clicks by half if you allow to slide open the menus on over which users can decide to enable/disable.. Also since I have a small 15 screen i have to scroll down to select settings menu when any other is open. an option to forget menu state might help

Attachments (1)

menu.diff (4.4 KB) - added by g0wda 5 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 in reply to: ↑ description g0wda5 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Replying to g0wda:

You can reduce the number of clicks by half if you allow to slide open the menus on over which users can decide to enable/disable.. Also since I have a small 15 screen i have to scroll down to select settings menu when any other is open. an option to forget menu state might help

g0wda5 years ago

comment:2 DD325 years ago

  • Keywords has-patch dev-feedback added
  • Resolution fixed deleted
  • Status changed from closed to reopened

Please do not close tickets as 'fixed' until the changes have been commited to the WordPress Core.

comment:3 janeforshort5 years ago

I'm not in favor of this based on feedback we received when discussing menu options with users during testing and development phases for 2.7. I think this would make an excellent plugin, but should not be in core.

comment:4 mrmist5 years ago

  • Milestone changed from 2.7.1 to 2.8

-1.

I don't like hover-open menues either. So at most I'd want this to be a choosable option.

Changing milestone - isn't 2.7.1 suppose to be bug fixes?

comment:5 jacobsantos5 years ago

  • Keywords Menu screen options dev-feedback removed
  • Milestone 2.8 deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed

Seems like a won't fix to me. The behavior is intentional and can almost completely be possible to override with a plugin.

Note: See TracTickets for help on using tickets.