Skip to content
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

Not all tabs are shown since Aug 12 or 13 update #90

Closed
sinyb opened this issue Aug 14, 2022 · 3 comments
Closed

Not all tabs are shown since Aug 12 or 13 update #90

sinyb opened this issue Aug 14, 2022 · 3 comments

Comments

@sinyb
Copy link

sinyb commented Aug 14, 2022

Hello!
Since yesterdays update (maybe a day or two earlier, I did not update my Nightly for a few days), maximum of two rows are ever shown, and even then some tabs are missing. Happens in Linux (openSUSE Tumbleweed) and Windows 11.
In Developer edition 104.x everything is OK, all 54 tabs visible, but in Nightly I can see only 3-4 tabs comming after 25 pinned ones (I usually have 30 pinned, but tried to reduce the number for test - did not help). On Aug 11 everything was fine.
It seems that there is something wrong with the width of the tab bar, so Firefox "thinks" that there is much more space that there actualy is and places tabs beyond the window/screen width. When I open new tab (Ctrl-T), one tab appears in second row for every 3 new tabs I open.

@enki1337
Copy link

Same problem here as well on Windows 7. Looks like something in the nightly messed things up.

@gammy
Copy link

gammy commented Aug 16, 2022

Replicated on 105.0a1 (2022-08-15) as well (Artix Linux (rolling)). Paxmod seems unaware of the width of the window; changing width of the browser has no effect on the positioning/size/rows of tabs.

numirias added a commit that referenced this issue Aug 16, 2022
@numirias
Copy link
Owner

Thanks guys for reporting. Should be fixed in the latest release, otherwise feel free to reopen.

I also put up a wiki page about how you can help pinpoint a bug by testing which exact build introduced a bug. Diffing the code then usually makes it fairly straightforward to see what caused it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants