[Ext] Classic Theme Restorer
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
ok, but the height is still not readjusted to narrow. Can we make the close button bold as well?
I have "@import url(./css/tabs/tab_close_always_visible.css); /**/" enabled. Is that interfering. It says use only one.
Should your default_tabs_tab_border.css work with these changes? Trying to make the border just a tiny bit mor defined. I have "classic squared tabs' disabled, but the changes I made have no effect
https://github.com/Aris-t2/CustomCSSfor ... border.css
I have "@import url(./css/tabs/tab_close_always_visible.css); /**/" enabled. Is that interfering. It says use only one.
Should your default_tabs_tab_border.css work with these changes? Trying to make the border just a tiny bit mor defined. I have "classic squared tabs' disabled, but the changes I made have no effect
https://github.com/Aris-t2/CustomCSSfor ... border.css
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
I don't know why your tab height does not adjust correctly, you have seen my screenshots. Test a new browser profile without any other tweaks/add-ons.
The "only use one" settings simulate a menu list or a radio list and only indicate to not use more than one from that group. Something like option1, option2, ....
"Should your default_tabs_tab_border.css work with these changes?"
Just test the code, why wait for an answer?
Here is what I got now with your modified code and a few tweaks.
Use this in addition to the above, if you are not using the projects classic tabs. You will also have to modify some of the start/end paddings/margins to save more space when using default tabs, but I hope you get the idea.
The "only use one" settings simulate a menu list or a radio list and only indicate to not use more than one from that group. Something like option1, option2, ....
"Should your default_tabs_tab_border.css work with these changes?"
Just test the code, why wait for an answer?
Here is what I got now with your modified code and a few tweaks.
Code: Select all
/* tab height */
#tabbrowser-tabs,
#tabbrowser-tabs > .tabbrowser-arrowscrollbox,
.tabbrowser-tabs[positionpinnedtabs] > .tabbrowser-tab[pinned] {
min-height: 19px !important;
/*height: 19px !important;*/ /* this might be required for some OS themes */
}
#TabsToolbar #tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
min-height: 18px !important;
max-height: 18px !important;
}
#TabsToolbar .tabbrowser-tab {
height: 19px !important;
min-height: 19px !important;
max-height: 19px !important;
}
/* tab label */
.tab-label {
-moz-box-flex: 1 !important;
text-align: center !important;
font-weight: bold !important;
font-size: 16px !important;
margin-top: -5px !important;
-moz-margin-start: 0px !important;
-moz-margin-end: 0px !important;
-moz-padding-start: 0px !important;
-moz-padding-end: 0px !important;
}
/* close icon */
#TabsToolbar #tabbrowser-tabs .tabbrowser-tab:not([pinned]) .tab-close-button {
-moz-box-ordinal-group: 0 !important;
-moz-margin-start: -9px !important;
-moz-margin-end: 0px !important;
}
#main-window #navigator-toolbox #TabsToolbar .close-icon > .toolbarbutton-icon,
#main-window #navigator-toolbox #TabsToolbar .tab-content .close-icon {
min-width: 20px !important;
width: 20px !important;
min-height: 20px !important;
height: 20px !important;
}
/* NUMBERED TABS */
#tabbrowser-tabs{
counter-reset: n_tabs 0;
}
.tabbrowser-tab .tab-content {
-moz-padding-start: 0px;
}
.tabbrowser-tab .tab-content::before {
display: -moz-box;
-moz-padding-end: 8px;
counter-increment: n_tabs;
content: counter(n_tabs);
font-weight: bold !important;
font-size: 16px !important;
margin-top: -2px !important;
}
Code: Select all
/* for default tabs */
/* border */
.tabbrowser-tab {
border-top: 1px solid black !important;
border-left: 1px solid black !important;
border-right: 1px solid black !important;
}
.tabbrowser-tab .tab-background {
border: unset !important;
}
/* hide tab separators */
.tabbrowser-tab::after,
.tabbrowser-tab::before {
opacity: 0 !important;
border-image: unset !important;
border-image-slice: unset !important;
width: unset !important;
}
#tabbrowser-tabs[movingtab] > .tabbrowser-tab[beforeselected]:not([last-visible-tab])::after,
.tabbrowser-tab:not([selected]):not([afterselected-visible]):not([afterhovered]):not([first-visible-tab]):not(:hover)::before,
#tabbrowser-tabs:not([overflow]) > .tabbrowser-tab[last-visible-tab]:not([selected]):not([beforehovered]):not(:hover)::after {
content: unset !important;
display: unset !important;
}
/* fix new tab button width/height for default tabs */
#navigator-toolbox #TabsToolbar .tabs-newtab-button > .toolbarbutton-icon {
padding: 0px !important;
width: 16px !important;
height: 16px !important;
}
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
All good now. I didn't have to change any settings, just rearrange the order of some things . I had stuff like spofir's #all tabs.css (needed for some custom buttons) that I had to place below the tweaks you crafted. That took care of it.
Can we make the close button bold?
Can we make the close button bold?
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
^^
No, the tab close button is an icon/image (svg). We can change its width and height or point to a different icon. CustomCSSforFx offers a few different close icons.
No, the tab close button is an icon/image (svg). We can change its width and height or point to a different icon. CustomCSSforFx offers a few different close icons.
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
Aris wrote:^^
No, the tab close button is an icon/image (svg). We can change its width and height or point to a different icon. CustomCSSforFx offers a few different close icons.
I should have looked harder (lots of good stuff there). I didn't realize there was a "close icons for general ui and tabs" option under the "GENERAL UI" heading.
I was able to find your image page so I now "kinda" have a better idea how it works. I tried to adapt one of those chrome\css\generalui\close_icon files to look for an image locally (something to do with list-style-image: url?), but I couldn't get it right.
_______________________________
I'd like to address and get advice on another issue. I just came across that important bit about "Some CSS tweaks won't work, if '@namespace' references are used inside .css files!"
I mentioned the "stuff like spofir's #all tabs.css". I have 3 of those "button helpers" in userchrome.css, and they all work with '@namespace'
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
Use the whole package/release, look into the code and pay attention to the relative paths used for image files and the folders those images and css files are in. Its better to start with something that already works and modify stuff later.
---
When working with userChrome.css every code only gets registered for "xul" content (browser ui) while every code inside userContent.css is only applied on web content. There is no need to distinguish this by adding @namespace references like it was required in the past for complete themes and add-ons, that did not specify the area their code tried to overlay.
Using a wrong @namespace will cause the code to be ignored. Sometimes css files containing @namespace do not get imported into userChrome.css or userContent.css. That for the warning is part of the css file, because the project is modular. userChrome.css and userContent.css work as an options area where one can enable and disable options by importing css files or out-commenting their @import.
None of the code in the project failed to work without @namespace, so its safe to say there is no need for it.
---
When working with userChrome.css every code only gets registered for "xul" content (browser ui) while every code inside userContent.css is only applied on web content. There is no need to distinguish this by adding @namespace references like it was required in the past for complete themes and add-ons, that did not specify the area their code tried to overlay.
Using a wrong @namespace will cause the code to be ignored. Sometimes css files containing @namespace do not get imported into userChrome.css or userContent.css. That for the warning is part of the css file, because the project is modular. userChrome.css and userContent.css work as an options area where one can enable and disable options by importing css files or out-commenting their @import.
None of the code in the project failed to work without @namespace, so its safe to say there is no need for it.
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
I'm working on it. I think I get it, but I've gotta get back to the tab bar height adjustment for a moment.Aris wrote:Use the whole package/release, look into the code and pay attention to the relative paths used for image files and the folders those images and css files are in. Its better to start with something that already works and modify stuff later.
---
When working with userChrome.css every code only gets registered for "xul" content (browser ui) while every code inside userContent.css is only applied on web content. There is no need to distinguish this by adding @namespace references like it was required in the past for complete themes and add-ons, that did not specify the area their code tried to overlay.
Using a wrong @namespace will cause the code to be ignored. Sometimes css files containing @namespace do not get imported into userChrome.css or userContent.css. That for the warning is part of the css file, because the project is modular. userChrome.css and userContent.css work as an options area where one can enable and disable options by importing css files or out-commenting their @import.
None of the code in the project failed to work without @namespace, so its safe to say there is no need for it.
I'm using this
Code: Select all
/* HIDE MIN/MAX/CLOSE BUTTONS – breaks tab bar narrowness*/
#titlebar-buttonbox { display:none!important; } */
I found another way
Code: Select all
/* HIDE MIN/MAX/CLOSE BUTTONS */
/* normal window */
#titlebar-max {display:none !important;}
#titlebar-close {display:none !important;}
#titlebar-min {display:none !important;}
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
There is more than one way to hide items.
"display: none" and "visibility: collapse" remove the area the item was in. "visibility: hidden" keeps the area intact, but you can also change width and/or height values of an object to a minimum and lower its opacity. That way it still is technically present, but not visible.
I suggest to try something like this:
"display: none" and "visibility: collapse" remove the area the item was in. "visibility: hidden" keeps the area intact, but you can also change width and/or height values of an object to a minimum and lower its opacity. That way it still is technically present, but not visible.
I suggest to try something like this:
Code: Select all
#titlebar-max,
#titlebar-close,
#titlebar-min,
#titlebar-buttonbox {
min-width: 1px !important;
width: 1px !important;
max-width: 1px !important;
opacity: 0 !important;
}
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
That pretty much nullifies my added customizations
I think it would be best to post all the extra stuff I have included in userchrome.css so whatever may be a problem is edited
I think it would be best to post all the extra stuff I have included in userchrome.css so whatever may be a problem is edited
Code: Select all
/* AGENT_SHEET */
/* don't show back or forward buttons if there's nothing to go back or forward to show */
#ctraddon_back-button[disabled="true"],
#ctraddon_forward-button[disabled="true"],
#back-button[disabled="true"],
#forward-button[disabled="true"] {
display: none !important;
}
/* HIDE MIN/MAX/CLOSE BUTTONS - breaks tab bar narrowness*/
#titlebar-buttonbox { display:none!important; } */
/* TAB BAR DECREASE HEIGHT AND CENTER TAB TEXT - ARIS */
/* CLOSE BUTTON ON THE LEFT - RED CLOSE BUTTON - NUMBERED TABS - ARIS */
/* tab height */
#tabbrowser-tabs,
#tabbrowser-tabs > .tabbrowser-arrowscrollbox,
.tabbrowser-tabs[positionpinnedtabs] > .tabbrowser-tab[pinned] {
min-height: 19px !important;
/*height: 19px !important;*/ /* this might be required for some OS themes */
}
#TabsToolbar #tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
min-height: 18px !important;
max-height: 18px !important;
}
#TabsToolbar .tabbrowser-tab {
height: 19px !important;
min-height: 19px !important;
max-height: 19px !important;
}
/* tab label */
.tab-label {
-moz-box-flex: 1 !important;
text-align: center !important;
font-weight: bold !important;
font-size: 16px !important;
margin-top: -5px !important;
-moz-margin-start: 0px !important;
-moz-margin-end: 0px !important;
-moz-padding-start: 0px !important;
-moz-padding-end: 0px !important;
}
/* close icon */
#TabsToolbar #tabbrowser-tabs .tabbrowser-tab:not([pinned]) .tab-close-button {
-moz-box-ordinal-group: 0 !important;
-moz-margin-start: -9px !important;
-moz-margin-end: 0px !important;
}
#main-window #navigator-toolbox #TabsToolbar .close-icon > .toolbarbutton-icon,
#main-window #navigator-toolbox #TabsToolbar .tab-content .close-icon {
min-width: 20px !important;
width: 20px !important;
min-height: 20px !important;
height: 20px !important;
}
/* NUMBERED TABS */
#tabbrowser-tabs{
counter-reset: n_tabs 0;
}
.tabbrowser-tab .tab-content {
-moz-padding-start: 0px;
}
.tabbrowser-tab .tab-content::before {
display: -moz-box;
-moz-padding-end: 8px;
counter-increment: n_tabs;
content: counter(n_tabs);
font-weight: bold !important;
font-size: 16px !important;
margin-top: -2px !important;
}
/* REMOVE EDIT MENU (IF YOU ALREADY USE ALL THE KEYBOARD SHORTCUTS) */
#edit-menu { display: none !important; }
#file-menu { display: none !important; }
#view-menu { display: none !important; }
#history-menu { display: none !important; }
#bookmarksMenu { display: none !important; }
/* Added userChrome.js support to Firefox with just userChrome.css to activate toolbar buttons like "restart browser"- from sporif *************************/
/* https://gist.github.com/Sporif/db6b3440fba0b1bcf5477afacf93f875 *************************/
#alltabs-button {
-moz-binding: url(data:text/xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIj8+DQo8IS0tIENvcHlyaWdodCAoYykgMjAxNyBIYWdnYWkg
TnVjaGkNCkF2YWlsYWJsZSBmb3IgdXNlIHVuZGVyIHRoZSBNSVQgTGljZW5zZToNCmh0dHBzOi8vb3BlbnNvdXJjZS5vcmcvbGlj
ZW5zZXMvTUlUDQogLS0+DQoNCjwhLS0gUnVuIHVzZXJDaHJvbWUuanMvdXNlckNocm9tZS54dWwgYW5kIC51Yy5qcy8udWM
ueHVsLy5jc3MgZmlsZXMgIC0tPg0KPGJpbmRpbmdzIHhtbG5zPSJodHRwOi8vd3d3Lm1vemlsbGEub3JnL3hibCI+DQogICAgPG
JpbmRpbmcgaWQ9ImpzIiBleHRlbmRzPSJjaHJvbWU6Ly9nbG9iYWwvY29udGVudC9iaW5kaW5ncy90b29sYmFyYnV0dG9uLnh
tbCNtZW51Ij4NCiAgICAgICAgPGltcGxlbWVudGF0aW9uPg0KICAgICAgICAgICAgPGNvbnN0cnVjdG9yPjwhW0NEQVRBWw0KIC
AgICAgICAgICAgICAgIGlmKHdpbmRvdy51c2VyQ2hyb21lSnNNb2QpIHJldHVybjsNCiAgICAgICAgICAgICAgICB3aW5kb3cudXN
lckNocm9tZUpzTW9kID0gdHJ1ZTsNCiAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICAgICB2YXIgY2hyb21lRmlsZXMgPSBG
aWxlVXRpbHMuZ2V0RGlyKCJVQ2hybSIsIFtdKS5kaXJlY3RvcnlFbnRyaWVzOw0KICAgICAgICAgICAgICAgIHZhciB4dWxGaWxl
cyA9IFtdOw0KICAgICAgICAgICAgICAgIHZhciBzc3MgPSBDY1snQG1vemlsbGEub3JnL2NvbnRlbnQvc3R5bGUtc2hlZXQtc2V
ydmljZTsxJ10uZ2V0U2VydmljZShDaS5uc0lTdHlsZVNoZWV0U2VydmljZSk7DQogICAgICAgICAgICAgICAgDQogICAgICAgI
CAgICAgICAgd2hpbGUoY2hyb21lRmlsZXMuaGFzTW9yZUVsZW1lbnRzKCkpIHsNCiAgICAgICAgICAgICAgICAgICAgdmFyI
GZpbGUgPSBjaHJvbWVGaWxlcy5nZXROZXh0KCkuUXVlcnlJbnRlcmZhY2UoQ2kubnNJRmlsZSk7DQogICAgICAgICAgI
CAgICAgICAgIHZhciBmaWxlVVJJID0gU2VydmljZXMuaW8ubmV3RmlsZVVSSShmaWxlKTsNCiAgICAgICAgICAgICAgICAgI
CAgDQogICAgICAgICAgICAgICAgICAgIGlmKGZpbGUuaXNGaWxlKCkpIHsNCiAgICAgICAgICAgICAgICAgICAgICAgIGlmK
C8oXnVzZXJDaHJvbWV8XC51YylcLmpzJC9pLnRlc3QoZmlsZS5sZWFmTmFtZSkpIHsNCiAgICAgICAgICAgICAgICAgI
CAgICAgICAgICBTZXJ2aWNlcy5zY3JpcHRsb2FkZXIubG9hZFN1YlNjcmlwdFdpdGhPcHRpb25zKGZpbGVVUkkuc3
BlYywge3RhcmdldDogd2luZG93LCBpZ25vcmVDYWNoZTogdHJ1ZX0pOw0KICAgICAgICAgICAgICAgICAgICAgICAgf
Q0KICAgICAgICAgICAgICAgICAgICAgICAgZWxzZSBpZigvKF51c2VyQ2hyb21lfFwudWMpXC54dWwkL2kudGVzd
ChmaWxlLmxlYWZOYW1lKSkgew0KICAgICAgICAgICAgICAgICAgICAgICAgICAgIHh1bEZpbGVzLnB1c2goZmls
ZVVSSS5zcGVjKTsNCiAgICAgICAgICAgICAgICAgICAgICAgIH0NCiAgICAgICAgICAgICAgICAgICAgICAgIGVsc2UgaWY
oL1wuYXNcLmNzcyQvaS50ZXN0KGZpbGUubGVhZk5hbWUpKSB7DQogICAgICAgICAgICAgICAgICAgICAgICAgI
CAgaWYoIXNzcy5zaGVldFJlZ2lzdGVyZWQoZmlsZVVSSSwgc3NzLkFHRU5UX1NIRUVUKSkNCiAgICAgICAgICAgI
CAgICAgICAgICAgICAgICAgICAgc3NzLmxvYWRBbmRSZWdpc3RlclNoZWV0KGZpbGVVUkksIHNzcy5BR0VOVF9
TSEVFVCk7DQogICAgICAgICAgICAgICAgICAgICAgICB9DQogICAgICAgICAgICAgICAgICAgICAgICBlbHNlIGlmKC9e
KD8hKHVzZXJDaHJvbWV8dXNlckNvbnRlbnQpXC5jc3MkKS4rXC5jc3MkL2kudGVzdChmaWxlLmxlYWZOYW1
lKSkgew0KICAgICAgICAgICAgICAgICAgICAgICAgICAgIGlmKCFzc3Muc2hlZXRSZWdpc3RlcmVkKGZpbGVVUkksI
HNzcy5VU0VSX1NIRUVUKSkNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgc3NzLmxvYWRBbmRSZWdpc
3RlclNoZWV0KGZpbGVVUkksIHNzcy5VU0VSX1NIRUVUKTsNCiAgICAgICAgICAgICAgICAgICAgICAgIH0NCiAgI
CAgICAgICAgICAgICAgICAgfQ0KICAgICAgICAgICAgICAgIH0NCiAgICAgICAgICAgICAgICANCiAgICAgICAgICAgICAgI
CBzZXRUaW1lb3V0KGZ1bmN0aW9uIGxvYWRYVUwoKSB7DQogICAgICAgICAgICAgICAgICAgIGlmKHh1bEZpb
GVzLmxlbmd0aCA+IDApIHsNCiAgICAgICAgICAgICAgICAgICAgICAgIGRvY3VtZW50LmxvYWRPdmVybGF5KHh1b
EZpbGVzLnNoaWZ0KCksIG51bGwpOw0KICAgICAgICAgICAgICAgICAgICAgICAgc2V0VGltZW91dChsb2FkWF
VMLCA1KTsNCiAgICAgICAgICAgICAgICAgICAgfQ0KICAgICAgICAgICAgICAgIH0sIDApOw0KICAgICAgICAgICAg
XV0+PC9jb25zdHJ1Y3Rvcj4NCiAgICAgICAgPC9pbXBsZW1lbnRhdGlvbj4NCiAgICA8L2JpbmRpbmc+DQo8L2JpbmRpbmdzPg==);
}
/* Copyright (c) 2017 Haggai Nuchi
Available for use under the MIT License:
https://opensource.org/licenses/MIT
*/
@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul);
toolbarbutton#alltabs-button {
-moz-binding: url("userChrome.xml#js");
}
/* Firefox userChrome.css - FOR EXITFIREFOXBUTTON_MOVABLE.UC.JS */
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
toolbarbutton#alltabs-button {
-moz-binding: url("userChrome.xml#js");
}
#go-quit-application-button {
list-style-image: url("exit.png") !important;
-moz-image-region: rect(0px, 16px, 16px, 0px) !important;
}
/* Firefox userChrome.css - FOR OPEN PROFILE DIRECTORY BUTTON */
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
toolbarbutton#alltabs-button {
-moz-binding: url("userChrome.xml#js");
}
#launch-profile-directory {
list-style-image: url("launch.png") !important;
-moz-image-region: rect(0px, 16px, 16px, 0px) !important;
Last edited by LIMPET235 on July 5th, 2018, 6:45 am, edited 1 time in total.
Reason: Edited the code as it was breaking the forum layout.
Reason: Edited the code as it was breaking the forum layout.
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
Edit your post and remove this line btw. the corresponding rule:
-moz-binding: url(data:text/xml;base64,....
It breaks this forums appearance and is not required in your code. You rebind alltabs button like two times after that again.
I strongly suggest to use a proper editing software with code highlighting like Notepad++. Your code had a few errors, which you probably missed, because default text editors do not highlight anything.
Remove you code from userChrome.css and replace it with this one:
-moz-binding: url(data:text/xml;base64,....
It breaks this forums appearance and is not required in your code. You rebind alltabs button like two times after that again.
I strongly suggest to use a proper editing software with code highlighting like Notepad++. Your code had a few errors, which you probably missed, because default text editors do not highlight anything.
Remove you code from userChrome.css and replace it with this one:
Code: Select all
/* don't show back or forward buttons if there's nothing to go back or forward to show */
#ctraddon_back-button[disabled="true"],
#ctraddon_forward-button[disabled="true"],
#back-button[disabled="true"],
#forward-button[disabled="true"] {
display: none !important;
}
/* HIDE MIN/MAX/CLOSE BUTTONS - breaks tab bar narrowness*/
#titlebar-max,
#titlebar-close,
#titlebar-min,
#titlebar-buttonbox {
min-width: 1px !important;
width: 1px !important;
max-width: 1px !important;
opacity: 0 !important;
}
/* TAB BAR DECREASE HEIGHT AND CENTER TAB TEXT - ARIS */
/* CLOSE BUTTON ON THE LEFT - RED CLOSE BUTTON - NUMBERED TABS - ARIS */
/* tab height */
#tabbrowser-tabs,
#tabbrowser-tabs > .tabbrowser-arrowscrollbox,
.tabbrowser-tabs[positionpinnedtabs] > .tabbrowser-tab[pinned] {
min-height: 19px !important;
/*height: 19px !important;*/ /* this might be required for some OS themes */
}
#TabsToolbar #tabbrowser-tabs[overflow="true"] .tabbrowser-tab[pinned] {
min-height: 18px !important;
max-height: 18px !important;
}
#TabsToolbar .tabbrowser-tab {
height: 19px !important;
min-height: 19px !important;
max-height: 19px !important;
}
/* tab label */
.tab-label {
-moz-box-flex: 1 !important;
text-align: center !important;
font-weight: bold !important;
font-size: 16px !important;
margin-top: -5px !important;
-moz-margin-start: 0px !important;
-moz-margin-end: 0px !important;
-moz-padding-start: 0px !important;
-moz-padding-end: 0px !important;
}
/* close icon */
#TabsToolbar #tabbrowser-tabs .tabbrowser-tab:not([pinned]) .tab-close-button {
-moz-box-ordinal-group: 0 !important;
-moz-margin-start: -9px !important;
-moz-margin-end: 0px !important;
}
#main-window #navigator-toolbox #TabsToolbar .close-icon > .toolbarbutton-icon,
#main-window #navigator-toolbox #TabsToolbar .tab-content .close-icon {
min-width: 20px !important;
width: 20px !important;
min-height: 20px !important;
height: 20px !important;
}
/* NUMBERED TABS */
#tabbrowser-tabs{
counter-reset: n_tabs 0;
}
.tabbrowser-tab .tab-content {
-moz-padding-start: 0px;
}
.tabbrowser-tab .tab-content::before {
display: -moz-box;
-moz-padding-end: 8px;
counter-increment: n_tabs;
content: counter(n_tabs);
font-weight: bold !important;
font-size: 16px !important;
margin-top: -2px !important;
}
/* REMOVE EDIT MENU (IF YOU ALREADY USE ALL THE KEYBOARD SHORTCUTS) */
#edit-menu { display: none !important; }
#file-menu { display: none !important; }
#view-menu { display: none !important; }
#history-menu { display: none !important; }
#bookmarksMenu { display: none !important; }
/* Firefox userChrome.css - FOR EXITFIREFOXBUTTON_MOVABLE.UC.JS */
toolbarbutton#alltabs-button {
-moz-binding: url("userChrome.xml#js");
}
#go-quit-application-button {
list-style-image: url("exit.png") !important;
-moz-image-region: rect(0px, 16px, 16px, 0px) !important;
}
/* Firefox userChrome.css - FOR OPEN PROFILE DIRECTORY BUTTON */
toolbarbutton#alltabs-button {
-moz-binding: url("userChrome.xml#js");
}
#launch-profile-directory {
list-style-image: url("launch.png") !important;
-moz-image-region: rect(0px, 16px, 16px, 0px) !important;
}
/* fix tab toolbars button width/height for default tabs */
#navigator-toolbox #TabsToolbar .scrollbutton-up,
#navigator-toolbox #TabsToolbar .scrollbutton-down,
#navigator-toolbox #TabsToolbar #alltabs-button,
#navigator-toolbox #TabsToolbar #new-tab-button {
padding: 0px !important;
}
#navigator-toolbox #TabsToolbar .scrollbutton-up > .toolbarbutton-icon,
#navigator-toolbox #TabsToolbar .scrollbutton-down > .toolbarbutton-icon,
#navigator-toolbox #TabsToolbar #alltabs-button > .toolbarbutton-icon,
#navigator-toolbox #TabsToolbar #new-tab-button > .toolbarbutton-icon,
#navigator-toolbox #TabsToolbar .tabs-newtab-button > .toolbarbutton-icon {
padding: 0px !important;
width: 16px !important;
height: 16px !important;
}
/* hide empty space before and after tabs */
hbox[type="pre-tabs"],
hbox[type="post-tabs"] {
min-width: 1px !important;
width: 1px !important;
max-width: 1px !important;
opacity: 0 !important;
}
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
Thanks Aris. Much appreciated.
I'll move any further inquiries to github if you wish.
I'll move any further inquiries to github if you wish.
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
That would be better.
If you have a problem with the code CustomCSSforFx provides or found a bug, open a new issue, read issue templates instructions and fill in the form (see points 1-5).
If you have a general question about code, add-ons or whatsoever, use the already available thread "General discussions, feedback, questions belong here".
Edit
There is no "requests area" here or there, but you can ask for assistance/help regarding your code or custom tweaks in "General discussions, feedback, questions belong here" thread on Github.
If you have a problem with the code CustomCSSforFx provides or found a bug, open a new issue, read issue templates instructions and fill in the form (see points 1-5).
If you have a general question about code, add-ons or whatsoever, use the already available thread "General discussions, feedback, questions belong here".
Edit
There is no "requests area" here or there, but you can ask for assistance/help regarding your code or custom tweaks in "General discussions, feedback, questions belong here" thread on Github.
Last edited by Aris on July 6th, 2018, 6:04 pm, edited 1 time in total.
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
It's ok to just post requests there like here?
- DanRaisch
- Moderator
- Posts: 127246
- Joined: September 23rd, 2004, 8:57 pm
- Location: Somewhere on the right coast
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
No, it's not a discussion forum. It's for the posting of bug reports or providing additional case data demonstrating previously posted bugs.
-
- Posts: 129
- Joined: June 16th, 2015, 10:59 am
Re: [Ext] Classic Theme Restorer (Fx29-56/Waterfox/Basilisk)
So whre's the place for this type of discussion?