-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Now it takes a lot of clicks to set a link to open in a new tab #53463
Comments
@Mamaduka So a new feature is released without being ready? Anyway, the problem is not solved with this PR, you still have to give a lot of clicks, it doesn't solve anything... |
Sorry, that wasn't my intention. #52799 wasn't ready for WP 6.3, but it might be included in the next minor release. Happy to keep the conversation open for now. cc @getdave, @richtabor |
It's all iteration—this is a step towards allowing more controls within the link editing experience as requested often (#13542 and #23011). There's a long list of continued improvements/enhancements around linking holistically tracked in #50891, but in particular #50892, and #52799 tidy this flow up a good bit. There shouldn't be so many steps between adding the link, then configuring it further (with even more options in the future). |
Thanks for the answers. Sorry for my irritation, but the additional work I'm going to have with this new WordPress is very frustrating. |
Really appreciate your feedback! |
Closed as a duplicate of #52216. |
I was shocked with this WordPress update.
Now to set a link to open it in a new tab you need to do a lot of clicks. This is hilarious.
I already mentioned, I don't know who makes these kind of decisions, but it seems that they don't use Wordpress on a daily basis.
For those who write a few posts sporadically this is not a problem, but for those who write daily it greatly increases the workflow.
This UX for setting a link to open in a new tab is terrible, it doesn't make any sense, I was stunned by it. Now I have a lot more work.
Please leave it as it was.
The text was updated successfully, but these errors were encountered: