-
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 8 replies
-
Could you test 4.1.8 release? |
Beta Was this translation helpful? Give feedback.
-
I am not sure what changed. So far as I can tell nothing changed. The height of the tabs still looks the same between 4.17 and 4.18 .. and the dark tabs are still too dark. Still hard to read the black text on it. Or perhaps there is another setting somewhere? |
Beta Was this translation helpful? Give feedback.
-
I'm not sure, if the issue is caused by your configuration of userChrome.css or by the active theme. Is it possible to post a screenshot of how the default setup looks without modifying userChrome.css? |
Beta Was this translation helpful? Give feedback.
-
This is what it looks like with your addon removed. I also have this code in the my_userChrome.css file: .tab-background { -moz-box-direction: reverse } /* to place color bar on multipcontainer on top instead of bottom */ /* to remove limitation of sidebar size */ #sidebar { #tabbrowser-tabs .tab-context-line {display: none;} /* 2px container line */ #tabbrowser-tabs .tab-background {border-bottom: solid 2px var(--identity-icon-color) !important;} /* 2px highlight line for active tab */ #TabsToolbar .tabbrowser-tab { ****** EDIT ****** I removed my_userChrome.css ..... all that did was make the tabs less tall and I lost the multi-account container colour lines (the blue line in the screenshots. So the gray bars and narrowness is not from there. Perhaps one of the options I enabled. So far as I know, I made the same changes that v4.05 had. Maybe I missed something, but not sure which option did this. I am using LiteFox 2.0 theme. |
Beta Was this translation helpful? Give feedback.
-
I meant a screenshot of the unmodified full setup of this projects files (without any other code). I've tested a few tab appearance settings and themes with this result: |
Beta Was this translation helpful? Give feedback.
-
The above screen shot is your default project with no changes. The above screenshot is FF default, with an empty Chrome folder. The above screenshot is what I had with v4.05 installed. |
Beta Was this translation helpful? Give feedback.
-
Looks like you used these in 4.0.5: And you might have changed tab height in general_variables.css too. |
Beta Was this translation helpful? Give feedback.
-
i dont recall changing anything other than the my_userchrome.css .... When I install a new version this is what I do:
I never went into general_variables. I would not even know what to touch. I would have sent a message here before thinking about changing anything. I know nothing about programming, so I would be very surprised if I would go in there to poke around. I am too afraid I'd break something and not know how to fix it. I would be quite happy to have the tabs as big as they are if I do not have your script running. As soon as I install your script, even without me changing anything, the tab height shrinks and it goes dark. I have: @import "./css/tabs/classic_squared_tabs.css"; // tabs_container_indicator_for_classic_squared_tabs.css --- Not enabled The only option I have enabled in the other tab settings: @import "./css/tabs/tab_icon_colors.css"; /**/ |
Beta Was this translation helpful? Give feedback.
-
Here is an issue which might or might not be related. I use tabs above the navigation toolbar, classic squared tabs. On my home computer and notebook, tab titles look like this, with the text vertically aligned in the middle: However, on my work computer, it now looks like this, with the text aligned to the bottom: This is quite perplexing, because all settings should be the same: the latest version of Windows 10 and FF v100.0 64-bit on all three machines, CustomCSS v4.1.7 is exactly the same (after customization, I copied the chrome library on my home computer into the chrome library on the other two machines), extensions are the same, toolbar is set up to look the same, all about:config settings containing the terms "proton" or "tabs" are identical, toolkit.legacyUserProfileCustomizations.stylesheets and browser.compactmode.show are set to "true" and browser.urlbar.update1 to "false". I seem to remember that I had a similar issue after an earlier FF update maybe a year ago, and even wrote about it here; unfortunately, I couldn't find it in the archives, nor remember what was the solution. Any ideas? Maybe I overlooked another about:config setting? |
Beta Was this translation helpful? Give feedback.
-
How is it when I install your script, with no changes (default settings) the change is so drastic? the tabs go dark on me and they squish down. Ultimately, what I want is the tabs to be higher. Either same height as if I had nothing in the Chrome directory, or maybe a little smaller. with my v4.05 it was perfect. So I am not sure what I missed to make it go dark, but the fact that it did that even without me making any changes has me curious. |
Beta Was this translation helpful? Give feedback.
-
I still can not reproduce your issue. |
Beta Was this translation helpful? Give feedback.
-
Link to my theme: https://addons.mozilla.org/en-CA/firefox/addon/litefox/ in the attachment, I included 2 chrome files the one with 418 is the one with v3 I used ( I tried to match 405 and 418 as best I could. Some of the options are not physically located in the same place)... and the 405 is your version v4.05. it works fine. The colours are a little off in FF100, but it is better than v4.18. I only wanted to change it because the colours in the addons and theme menu are off. But If you install my theme, and just add your Chrome file in its default state, you can tell the tab height and dark tabs. |
Beta Was this translation helpful? Give feedback.
-
I suggest to disable Not sure why the ui differs that much now, but it might be related to latest lw-theme changes by Mozilla. |
Beta Was this translation helpful? Give feedback.
I suggest to disable
classic_squared_tabs.css
and switch toclassic_squared_tabs_australized.css
,default_tabs_enhanced.css
ordefault_tabs_photon.css
. They might be closer to what you have had before.Not sure why the ui differs that much now, but it might be related to latest lw-theme changes by Mozilla.