MacOS "Tabs on the right" option not functional

[talonlikeaclaw]

What happened?

When opening the context menu in the Vertical Tab Bar and selecting "Tabs on the right" on my M3 Pro Macbook, nothing happens. However, when I perform the same action on my Windows 11 PC, it functions as expected. There is a check mark present on the option after selecting it on MacOS, but the Vertical Tab Bar remains on the left side.

Reproducible?

• I have checked that this issue cannot be reproduced on Mozilla Firefox.

Version

1.0.0-a.23

Severity impact

Low

What platform are you seeing the problem on?

macOS - aarch64

Relevant log output

No response

[soumendrak]

Yes, Tab on right just suffixes the dropdown value with a check mark and nothing moves.

[mr-cheffy]

Let's see for the next release if this is fixed, im not on mac so I can't really test it

[talonlikeaclaw]

@mauro-balades Still no luck as of version 1.0.0-a.28. I'll keep you updated in future versions!

[fpigeonjr]

confirmed on

• System Version: macOS 14.6.1 (23G93)
• Kernel Version: Darwin 23.6.0

[ventsislav-georgiev]

I have the opposite issue. My tabs swapped on the right after some restart without me cliking on that option. I can't find a way to revert them back to normal.

v 1.0.0-a.33 (64-bit) on M1

[ventsislav-georgiev]

Another note: enabling compact mode shows them on the left.

Screen.Recording.2024-08-30.at.22.27.29.mov

[ventsislav-georgiev]

More info: I've managed to "fix" my tabs stuck on the right only behavior by toggling the Sidebar. That magically moved the tab bar on the left again instantly. 🤷🏻‍♂️

Now changing the sidebar location seems to change the tabs location as well. Here is a video of this behavior:
https://github.com/user-attachments/assets/22a5630c-6744-4de8-83b0-e525a81273b0

This however no longer preserves after restarts. Now they are back to the left on start. 😄

[r-nl]

This issue still persists on a fresh install, it it stuck eternally on the left. On OSX, this also means the window controls are offset, which is subideal.

[mr-cheffy]

I think both issues are fixed for the next release, we'll see

[talonlikeaclaw]

@mauro-balades Unfortunately the issue seems to persist on 1.0.1-a. Love the update though, great job!