-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revise Link Control design and UX #47310
Comments
@jameskoster Does the ellipsis icon for "Link options" make sense here? |
Pasting this response from the old reference point:
|
Iirc all instances of the ellipsis icon open popover menus. Are you suggesting to employ that pattern and putting the settings in a popover? Or to retain the behaviour in the design above and just change the icon? The former might feel a bit awkward (popover within a popover) and the latter feels like a it breaks an existing design convention. Another option could be the Or even just a chevron? 🤔 Though I think that looks a little strange without a text label. |
The settings icon looks good. |
FYI I flagged this in the Accessibility channel on WP Slack (requires signup). Also added the appropriate label to ensure we're looping folks in early for feedback. |
Also noting that I remember a while back there were some folks who were against adding lots of settings controls to this interface. That said I'm aware of several requests for more fine grained settings controls such as those offered by Yoast (which they currently add by re-implementing the Link Control in their Plugin). It's worth noting that there is currently no simple way to allow users to customise/extend the settings controls because whilst it's trivial to pass props to |
A few comments from an accessibility standpoint:
|
Good idea.
I suspect linking to the media file is a very common use case so perhaps we'd need the shortcuts to begin with? A dropdown might work: Alternatively, we could avoid a dropdown altogether by simply pre-populating the destination with the associated token? |
The token looks good. Is the radius 2px? Looks 3px. Maybe needs to be an inset border |
@joedolson Thank you for taking the time to feedback here. I'll spin out Issues from your comment. Update: I created Issues and included ones that are specifically related to the re-design in the Issue description above. |
Is there a way to keep the settings drawer open by default? Is it this issue by any chance? Otherwise if you want to link to a new tab, you need to click quite a few times to get that done. I currently have 15.2.4 installed in my test site. |
Yes we're working on that one. |
Related #35073 |
@getdave are we able to link this new issue here? It suggests a few changes including always showing open in new tab setting which might conflict with this issue. I'm struggling a little bit keeping up with all the navigation issues and it seems like a couple of them overlap. Let me know if I can help break the above one down into smaller tasks. |
Thanks you for picking up and wrangling some of this. I'm intending to get onto this myself as my next priority (after some other pressing issues that are time sensitive).
I'm concerned that Link Control needs to be considered in a holistic sense outside of just creation of links in the Nav block. In fact much of what we are landed with now is partly due to an over-focus on servicing the Nav block. The aim of #47310 was to be a canonical place where we could do that. Then once good decisions have been made to service the entirety of the editor we can adjust them to better work for the Nav block. Ideally we'd use #47310 as a canonical source of truth. We can adjust it as necessary. I'm very keen we don't loose sight of the the reason for the creation of the "settings drawer" which is to allow for the much requested addition of ancillary controls for links. |
I've created this Issue which tracks the next iteration of the Link UI. I'll leave this Issue open for now but the overview can be found there. |
Closing in favour of #50891 |
Let's update the Link Control design and UX to match the design provided by @jameskoster in #46891 (comment).
Quoting from @jameskoster
PRs
Visual UX
a11y
Bugs introduced by the above changes
Please don't put general bugs in here. This is reserved for bugs introduce specifically by any of the changes above.
The text was updated successfully, but these errors were encountered: