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

[Bug] tab appearance in incognito tabs seems broken #3547

Closed
shadoxxhd opened this issue May 12, 2024 · 3 comments
Closed

[Bug] tab appearance in incognito tabs seems broken #3547

shadoxxhd opened this issue May 12, 2024 · 3 comments

Comments

@shadoxxhd
Copy link

Abstract

In incognito windows, many tabs take up multiple "lines" in the vertical view:
image
Also, the order icon/title/X is effectively reversed for the "single line" entries.

In normal windows, the tab list looks like it should (normal proton style without customizations)

Steps to reproduce

I updated the extension, and suddenly the formatting was broken.
Disabling and re-enabling the extension and giving the TST addons access to private windows (or revoking it) didn't change the issue.
I don't have any environments to recreate the issue right now.

Expected result

Private window tabs look like normal tabs.

Actual result

They don't (see screenshot above).

Environment

  • Platform (OS): Win10
  • Version of Firefox: 120.0
  • Version (or revision) of Tree Style Tab: 4.0.14
@shadoxxhd
Copy link
Author

Other themes have similar issues.

@piroor
Copy link
Owner

piroor commented May 12, 2024

Could you post "expected" case screenshot too? TST's appearance is affected from various reasons - language, platform color scheme, and so on, so I don't know what is exact expected case on your environment.

@shadoxxhd
Copy link
Author

shadoxxhd commented May 13, 2024

image
"expected" demonstration (different sites, but same configuration, apart from column width).

Interestingly, after I killed the GPU process for RAM recovery reasons, the problem fixed itself - private tabs look like normal for me now. Since this might have been a random, transient, inherently unreplicable issue (flipped bit in memory perhaps?), I'll close the issue for now.

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

No branches or pull requests

2 participants