Make WordPress Core

Opened 3 months ago

Last modified 9 days ago

#60763 new enhancement

Allow resizing the individual content areas in Appearance / Menus

Reported by: namithjawahar's profile namith.jawahar Owned by:
Milestone: 6.6 Priority: normal
Severity: normal Version:
Component: Menus Keywords: has-patch needs-design-feedback
Focuses: ui, css, administration Cc:

Description

The space to select posts, pages and custom posts for dropping into the menu is restricted to 200px height which makes it really difficult to select posts/pages when creating/editing menus.
The user experience will be greatly improved if the section can be resized.

Attachments (1)

Menu Resize.png (26.3 KB) - added by namith.jawahar 3 months ago.
Resizable Menu

Download all attachments as: .zip

Change History (9)

@namith.jawahar
3 months ago

Resizable Menu

#2 @sabernhardt
2 months ago

  • Focuses administration added; accessibility removed
  • Summary changed from Allow resizing the indivigual content areas in Appearance / Menus to Allow resizing the individual content areas in Appearance / Menus
  • Version trunk deleted

This ticket was mentioned in Slack in #core by namithjawahar. View the logs.


5 weeks ago

#4 follow-up: @NekoJonez
5 weeks ago

  • Focuses accessibility added

Two things, I would like to see what #Design and #Accessability think here so nothing goes wrong here.

Also, it that feature only for the first pages div or all of them?

#5 @jorbin
5 weeks ago

  • Keywords needs-design-feedback added
  • Milestone changed from Awaiting Review to 6.6

Milestoning so that this can be considered for 6.6. I would be interested in hearing if there are any design concerns with implementing this.

One note is that the resize property is only supported by 82% of browsers but I don't think that needs to be a blocker https://caniuse.com/css-resize

#6 @joedolson
5 weeks ago

It's worth noting that the resize property is supported by 98% of desktop browsers, and this issue isn't addressing the mobile UI for editing menus, which may not be helped significantly by this change, given the limited screen space generally.

On the accessibility front, while the resize handle doesn't have any keyboard accessibility built-in, that shouldn't be a blocker; it will be exactly the same experience as it is right now. This will improve things for some users, and should not make things worse for any users.

#7 in reply to: ↑ 4 @namith.jawahar
5 weeks ago

Replying to NekoJonez:

Also, it that feature only for the first pages div or all of them?

It targets all the divs, works for pages, custom post types, tags and everything else that might come in there. For things like Custom Links we can use a css selector to not show the resize option if preferred, but not implemented in this PR.

Last edited 5 weeks ago by namith.jawahar (previous) (diff)

#8 @joedolson
9 days ago

  • Focuses accessibility removed

I tested this and it works well and doesn't appear to interfere with the design in any noticeable way. I think this should move forward.

I'm removing the accessibility focus, however, as this has already received accessibility feedback and does not have any accessibility concerns.

Note: See TracTickets for help on using tickets.