"Open link in New Tab" does not follow the "Move the new tab button to the top" Setting
Captchas
- [x] I have read the instructions.
- [x] I have searched existing issues and avoided creating duplicates.
- [x] I am not filing an enhancement request.
- [x] I have checked that this issue cannot be reproduced on Mozilla Firefox.
- [x] I have checked that this issue can be reproduced once I removed all my Mods and Custom CSS.
What happened?
- Enable "Move the new tab button to the top"
- Go to any website.
- Middle Click or Right Click -> Open Link in New Tab on any url
Actual Result: New Tab Opens Below current Tab
Expected Result: New Tap Should Open above Current Tab
This is an updated version of #5091
Version
1.11.1b
What platform are you seeing the problem on?
Windows - x64
What component is this issue related to?
Tabs
Relevant log output if applicable
Reproduced on same version and same platform.
Clarifying post: This isn't referring to what the new tab button does. It's referring to where a middle-clicked or ctrl-clicked or Open Link in New Tab ends up in the tab list.
When enabled, if you open a new tab, it will spawn the new tab at the top of the vertical tab list. When disabled, if you open a new tab, it will spawn the new tab at the bottom of the vertical tab list.
I like this new spawning direction and I want the "Open link in New Tab" to be consistent with the new spawning direction. It currently spawns the tab just below the current tab, regardless of the new Spawning direction
Originally posted by @KenzKD in #5091
However, I'd note that the current behavior mirrors that of Chrome and Firefox, which is different from what you might be expecting: It sometimes will open tab(s) next to the tab where you clicked on the link. Here's what would happen if you middle-clicked a bunch of tabs from tab C:
| A | B | [C] | C6 | C7 | C1 | C2 | C3 | C4 | C5 | D | E |
|---|
Note that C6 and C7 are before C1-5. I'm not sure what causes this to happen, because sometimes the sequence will break after a while, i.e. you open C1-5, do something, and C6 might go before C1.
I believe this is actually expected behavior. Arc does it like this as well
Hi, @KenzKD. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.
Issue Summary:
- The "Open link in New Tab" feature does not adhere to the "Move the new tab button to the top" setting.
- New tabs open below the current tab instead of above on Windows x64 with version 1.11.1b.
- Kenblu24 confirms the issue, noting similar behavior in Chrome and Firefox.
- Mauro-balades suggests this might be expected behavior, similar to Arc.
- This issue is a continuation of a previously reported problem, #5091.
Next Steps:
- Please confirm if this issue is still relevant to the latest version of the desktop repository by commenting here.
- If there is no further activity, this issue will be automatically closed in 7 days.
Thank you for your understanding and contribution!
Yes, this issue is still relevant
Hi, @KenzKD. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.
Issue Summary:
- You reported that the "Open link in New Tab" feature does not adhere to the "Move the new tab button to the top" setting in version 1.11.1b for Windows x64.
- Kenblu24 confirmed the issue, noting similar behavior in Chrome and Firefox.
- mauro-balades suggested this might be expected behavior, similar to Arc.
- The issue is related to a previously reported problem, #5091.
Next Steps:
- Please confirm if this issue is still relevant to the latest version of the desktop repository by commenting here.
- If no further updates are provided, the issue will be automatically closed in 7 days.
Thank you for your understanding and contribution!
Yes, This is still relevant as of v1.13.1b
Hi, @KenzKD. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.
Issue Summary:
- You reported that the "Move the new tab button to the top" setting does not work as expected on Windows x64 version 1.11.1b.
- New tabs open below the current tab instead of above it when opening links in a new tab.
- Kenblu24 confirmed similar behavior in Chrome and Firefox, while mr-cheffy suggested it might be expected behavior similar to Arc.
- You confirmed the issue persists in version 1.13.1b.
Next Steps:
- Please let us know if this issue is still relevant to the latest version of the desktop repository by commenting here.
- If no further updates are provided, the issue will be automatically closed in 7 days.
Thank you for your understanding and contribution!
Yes, This is still relevant as of v1.14.5b.
I also think it should be its own setting so the user can choose how they want to handle the behavior of creating normal new tabs and opening links in new tabs.
Hi, @KenzKD. I'm Dosu, and I'm helping the desktop team manage their backlog and am marking this issue as stale.
Issue Summary:
- You reported that enabling "Move the new tab button to the top" does not change where new tabs from links open; they still open below the current tab.
- This behavior was confirmed by another user and noted to be similar in Chrome and Firefox.
- A suggestion was made that this might be expected behavior, referencing the Arc browser.
- You confirmed the issue persists through multiple versions (1.13.1b and 1.14.5b).
- You proposed adding a separate setting to control the behavior of opening new tabs from links independently.
Next Steps:
- Please let me know if this issue is still relevant with the latest version of the desktop app by commenting here to keep the discussion open.
- If I don’t hear back within 7 days, this issue will be automatically closed.
Thanks for your understanding and contribution!
Yes, This is still relevant as of v1.14.11b
Hi, @KenzKD. I'm Dosu (https://dosu.dev), and I'm helping the desktop team manage their backlog and am marking this issue as stale.
Issue Summary:
- You reported that with the "Move the new tab button to the top" setting enabled, new tabs opened from links appear below the current tab instead of above.
- This behavior has persisted across multiple versions (1.11.1b to 1.14.11b) on Windows x64.
- Another user confirmed this behavior and noted it matches Chrome and Firefox's behavior.
- A suggestion was made that this might be expected behavior, similar to the Arc browser.
- You proposed adding a separate setting to control new tab placement independently for normal tabs and link-opened tabs.
Next Steps:
- Please confirm if this issue is still relevant with the latest version of the desktop app.
- If it is, feel free to keep the discussion open by commenting on this issue; otherwise, I will automatically close it in 10 days.
Thanks for your understanding and contribution!
Yes, This is still relevant as of v1.17.7b