onemen wrote:
klb
Tabmix never used "browser.tabs.tabClipWidth" for setting Tab max width
this preference is use to control when to hide the close button on tabs that are smaller then the value of browser.tabs.tabClipWidth.
Tabmix use browser.tabs.tabMaxWidth and browser.tabs.tabMinWidth.
starting the latest build Tabmix no longer set tab with on each tab but uses dynamic css rule, the problem is that Classic Compact set min-width and max-width with !important so its override Tabmix settings.
in total we have 3 problems
1. you set max width by browser.tabs.tabClipWidth and tabmix by browser.tabs.tabMaxWidth
2. your css rule is for .tabbrowser-tab[fadein]:not([pinned]) Tabmix used only .tabbrowser-tab:not([pinned])
3. your css is with !important
my workaround for all of the above is to set in Tabmix this rule dynamically
Code:
.tabbrowser-tabs > .tabbrowser-tab:not([pinned]) {
min-width: 100px !important;
max-width: 250px !important;
}
This was helpful, I'm not sure how my confusion with tabClipWidth and tabMaxWidth came into being in CCO. I'll get this fixed with CCO v4.0.8.1 that I will push to AMO this weekend. Hopefully that will eliminate this conflict between our two addons.
Once we are using the same about:config setting for max tab width the problem will go away as users get upgraded to CCO v4.0.8.1.
We do seem to have a lot of overlapping users, as well as a lot of users we don't share. What I want to do is make things as seamless between our two addons as possible. We share two overlapping options. The first being the close tab button option and the second being the min/max tab width setting. My goal is to try and eliminate conflicts between our addons at this point of overlap. By fixing my tabClipWidth error I can eliminate one point of conflict.
--EDIT--
A patched version of CCO v4.0.8 has been uploaded to AMO that uses tabMaxWidth instead of tabClipWidth. I couldn't change the version number without losing my place in the approval queue so I left the version number alone. v4.0.9 will come along in a month or two which will replace any incorrect builds of v4.0.8.
Those users who experience a max tab width conflict between CCO and TMP on an older version of CCO should use CCO's max tab width option until they get an updated version of CCO with the fix. Once they have the fix they can use either CCO or TMP as they get settings from the same place.
_________________
Creator of Firefox theme
Classic Compact and its companion extension
Classic Compact Options