π Bug report
Latest master.
Editing link toolbar should appear. The link shouldn't be opened in a new tab.
Clicked link is opened in the new tab.
I am not sure it is a bug or not. If not, the ticket is invalid.
I forgot to mention about browsers⦠I can reproduce it on Firefox. On Chrome this behaviour does not occur. So it seems to be a bug.
I confirm that but...
...I also noticed this is a native feature of FF called "Open in Background Tab" https://support.mozilla.org/en-US/kb/mouse-shortcuts-perform-common-tasks, which can also be triggered by middle-clicking a link. I checked CKEditor 4 and it allows this behavior. I don't remember any bug reports concerning it in the past.
Anyway, neither Ctrl/Cmd+left click nor plain middle-click opens a new tab in Chrome. I checked that using plain contenteditable
so it's not precisely about CKEditor 5.
TBH, I wouldn't be worried about that. Even if a user uses this shortcut accidently, the link opens in a background tab which does not disrupt the editing process. What's more, instead of disabling it in FF, I'd rather consider implementing the feature for Google Chrome because it feels like a nice UX to me.
cc @Reinmar
What's more, instead of disabling it in FF, I'd rather consider implementing the feature for Google Chrome because it feels like a nice UX to me.
π π π
Most helpful comment
I confirm that but...
...I also noticed this is a native feature of FF called "Open in Background Tab" https://support.mozilla.org/en-US/kb/mouse-shortcuts-perform-common-tasks, which can also be triggered by middle-clicking a link. I checked CKEditor 4 and it allows this behavior. I don't remember any bug reports concerning it in the past.
Anyway, neither Ctrl/Cmd+left click nor plain middle-click opens a new tab in Chrome. I checked that using plain
contenteditable
so it's not precisely about CKEditor 5.TBH, I wouldn't be worried about that. Even if a user uses this shortcut accidently, the link opens in a background tab which does not disrupt the editing process. What's more, instead of disabling it in FF, I'd rather consider implementing the feature for Google Chrome because it feels like a nice UX to me.
cc @Reinmar