-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Th24 looks ugly when using some custom themes #863
Comments
Currently, th24 styles should only be adapted to the default theme. |
@gz83 @dnchshrp I can fix the white line outline on the omnibox. The white line under the bookmarks bar, im not sure what that is or why its doing that. The tab separators are not an issue (from a code perspective): they are behaving normally. Installing this theme on Chrome should also make the separators look like that. Removing the separators would fuck spacing up to no end, however, I might put a flag that tells them to be 0 opacity i.e. transparent to the color on the layer underneath it. The problem is that means yet another command line code path to maintain, just for you or the few that encounter this. While I want everyone to enjoy thorium, and I am definitely not above taking the time to fix something just for one person, I also have to balance how many times I do stuff like that. I am thinking this should be easy, so I can probably do it for you, but no promises, because if it takes above a certain amount of time or requires modifying too many files, I won't be able to justify it in my head |
OK, thanks for the response! @Alex313031 |
@gz83 Yes, but the ultimate goal is to have Th24 work seamlessly, meaning that themes should also work. The only thing I have no idea about is the whole bookmarks bar white line thing. |
System Details
M128
Problem
There are visible white lines that appear when using custom themes which makes the UI look ugly:
It also would be nice to be able to optionally make the tab separators invisible since they can look bad in some cases:
Did you read the FAQ?
Yes
Additional Notes
The text was updated successfully, but these errors were encountered: