#59054 closed defect (bug) (reported-upstream)
open in new tab toggle
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Editor | Keywords: | |
Focuses: | ui, accessibility | Cc: |
Description
Hey, thanks for the latest WP version 6.3. I wanted to remark that moving the "open in new tab" toggle one layer deeper into the UI is not a very helpful feature. It doesn't do anything for me that I now get less info when I click on a link in the editor. I constantly turn links into open in new tab ones and vice versa. Now I have to click into "Advanced" each time.
I hope other people will remark on this and it will be rolled back or at least give us an option.
Thanks!
-Nik
Attachments (1)
Change History (16)
#2
follow-up:
↓ 5
@
18 months ago
- Focuses ui added
This is actually a pretty common report at this point.
The issue was fixed and should ship with Gutenberg 16.4, but it missed the cutoff for WP 6.3
This ticket was mentioned in Slack in #forums by ipstenu. View the logs.
18 months ago
#5
in reply to:
↑ 2
@
18 months ago
Replying to Ipstenu:
This is actually a pretty common report at this point.
The issue was fixed and should ship with Gutenberg 16.4, but it missed the cutoff for WP 6.3
This most likely means this is for WordPress 6.4 since a minor release doesn't contain Gutenberg updates right unless they are critical bugs no?
#7
@
18 months ago
- Focuses accessibility added
This is a critical bug because it makes every help document redundant.
It is a bad UI / UX experience. I think it should be in 6.3.1 and would see it as a rather urgent update. It makes editing links a bad experience.
Added attachment with a screenshot of the editing experience VS the add.
It used to show the open tab box - also in image.
I noticed that WordPress.com updated all there documentation - why they dont update .org is a mystery.
Either way the new experience is confusing as the options on what to do with a link are gone and the highlight is also not working either. So once you open the link tool, the text you are linking is no longer highlighted.
Loom for that: https://www.loom.com/share/bf0977e95b10471eb83f0d5ed11cba54?sid=880d4685-7c92-4cbd-bb6a-eb27058a9351
This ticket was mentioned in Slack in #docs by zzap. View the logs.
18 months ago
This ticket was mentioned in Slack in #core-editor by nekojonez. View the logs.
18 months ago
#10
@
18 months ago
@NekoJonez I have no idea if it'll be in a minor release. Sorry :(
@mrkdevelopment Re this:
I noticed that WordPress.com updated all there documentation - why they dont update .org is a mystery.
Please remember that WordPress.com is a company and WordPress.org is a volunteer project. Basically, .com gets paid to keep all that up to date. Everything here? Not so much :)
This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.
18 months ago
#12
follow-up:
↓ 14
@
18 months ago
- Milestone Awaiting Review deleted
- Resolution set to reported-upstream
- Status changed from new to closed
This issue is being resolved in Gutenberg; I don't know what release it will be shipping in, but there's nothing more to be done about it on the core level, so I'm closing this as reported upstream. It has been flagged as a candidate for 6.3.1, but that does not mean that it will ship in 6.3.1.
#13
@
18 months ago
Glad to hear we'll see this issue gone in 6.4
Thanks to our developers!
Brass Ring Web Design
#14
in reply to:
↑ 12
@
17 months ago
Replying to joedolson:
This issue is being resolved in Gutenberg; I don't know what release it will be shipping in, but there's nothing more to be done about it on the core level, so I'm closing this as reported upstream. It has been flagged as a candidate for 6.3.1, but that does not mean that it will ship in 6.3.1.
Will link management get reverted exactly to the way it was? Honestly, the current implementation is driving me mad - and with me many, MANY others (just check out some of the other forums on this).
I wonder how such a horrific piece of UX made it through the beta testers? Are these people even WordPress users themselves?
Plus, I just can't help but wonder how this kind of "solution looking for a problem" type of feature bubbled up in the first place. There are real grievances real users have with Gutenberg, which are being completely ignored for months or even years now.
Given that, why bother with vanity projects such as these no one ever asked for?
Provide screenshots or videos for better comprehension of the issue. Thank you for the report.