#60763 closed enhancement (fixed)
Allow resizing the individual content areas in Appearance / Menus
Reported by: | namith.jawahar | Owned by: | joedolson |
---|---|---|---|
Milestone: | 6.6 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Menus | Keywords: | has-patch commit |
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)
Change History (15)
This ticket was mentioned in PR #6263 on WordPress/wordpress-develop by @namith.jawahar.
6 months ago
#1
#2
@
6 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 months ago
#4
follow-up:
↓ 7
@
5 months 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
@
5 months 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
@
5 months 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
@
5 months 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.
#8
@
4 months 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.
This ticket was mentioned in Slack in #core by nhrrob. View the logs.
4 months ago
This ticket was mentioned in Slack in #design by nhrrob. View the logs.
4 months ago
#11
@
4 months ago
- Keywords needs-design-feedback removed
Looks like the resize property is restricted to being vertical, so as a desktop affordance for this particular interface, it doesn't seem harmful to add.
#12
@
4 months ago
- Keywords commit added
- Owner set to joedolson
- Status changed from new to accepted
This looks good. I checked over the other containers impacted by the CSS; the taxonomy tab panel divs in the classic editor, and they do not appear to be effected by these changes.
I'll add a comment in the CSS to explain the 75px calc value, but otherwise this is good to go.
@joedolson commented on PR #6263:
4 months ago
#14
In r58256
Resizable Menu