Replies: 72 comments 154 replies
-
|
Hi Aris-t2, v4.6.9 My address bar is vertically off center. I've made vertical space adjustments for my toolbars. I mention that in case that is related?
|
Beta Was this translation helpful? Give feedback.
-
|
(repost) Hi,
Multirow tabs + classic drop indicator + tabs_below_navigation_toolbar (+ ...), and the tab drop indicator is clipped by the tab content (even with z-index 10000), do you know what to do? (Tab drop indicator with "multirow tabs" works well with the script https://github.com/TroudhuK/userChromeJS/blob/master/MultiRowTabLiteforFx.uc.js, the only problem I have is what I show on the capture.) |
Beta Was this translation helpful? Give feedback.
-
|
I have no fix for this. |
Beta Was this translation helpful? Give feedback.
-
|
isn't this the same problem that custom_backforward_connected_to_location_bar have that the z-index stop working after the update |
Beta Was this translation helpful? Give feedback.
-
|
The "go_button_in_location_bar_hidden.css" hides the Go button, but what about adding a CSS feature (CSS file) with the opposite effect? With effect which would make the Go, button in the address bar always show even if the address bar is unfocused? It would be very handy to have it because users would not need to click on the location bar to show a pop-up if they already have the URL typed... I propose the name "go_button_in_location_bar_always_show.css" |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if this is the right place to ask, but I haven't found a better one. It's not really related to this repository in particular, rather to a recent change in Firefox that broke my own custom css. If you like the idea of status in urlbar you're very much welcome to add it to the long list of your own tweaks, otherwise I'm just interested in learning if there's a simple way to restore z-positioning of 2 elements from a couple browser updates ago. In one of the recent firefox updates (a month? 2 months maybe?) I did try setting various elements to low/negative |
Beta Was this translation helpful? Give feedback.
-
|
I ended up just removing the Not sure if plain CSS could do the trick as well |
Beta Was this translation helpful? Give feedback.
-
|
Hello @Aris-t2,
For the addon bar I use :root {
--addonbar_height: 22px !important;
} |
Beta Was this translation helpful? Give feedback.
-
|
hello again. i asked how to remove tab scroll buttons, you adviced me to add this #scrollbutton-up[part="scrollbutton-up"][keyNav="false"][data-l10n-id="overflow-scroll-button-backwards"][tooltiptext], and this #scrollbutton-up[part="scrollbutton-up"][tooltiptext], first one workes, but if i drag tab it doesnt scroll, how to fix it? |
Beta Was this translation helpful? Give feedback.
-
|
@ Aris-t2 : I don't understand the format of this forum. Why all the articles/questions smashed together into one github entry? For example, when I read the above (about scrollbutton removal) I can not find that user's original question. |
Beta Was this translation helpful? Give feedback.
-
|
@joefiesta In GitHub there is an area for issue tickets and another for discussions. Right now we are in the latter. In issues when you write a comment it will be placed on its own in first level. But in discussions there are also replies possible which will appear right below the comment which was replied to, slightly indented and with a different background. For instance, you’ve replied to the question about the scroll arrow buttons, and I just now add a reply to you. You, instead, should have better used the “Add a comment” field slightly deeper, but I am answering you and so for me using the “Write a reply” is the right choice. (Don’t mind, I had to understand this myself in the past.) @trofey had asked under the slightly different name @trophhy in the prior, now closed discussion, see on Dec 2, 2024. |
Beta Was this translation helpful? Give feedback.
-
|
Thx. I get it. One issues per problem is nicer, but it has the problem of creating hundreds or thousands of separate issues, for example Autohotkey's forum. l thanks for you reply. |
Beta Was this translation helpful? Give feedback.
-
|
I know custom buttons are not supported here, but I have this one, aboutaddons-button.uc.js, that just stopped working/appearing in Fx 134.
Can I advice about where I might go to get help? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
We are still in the wrong repository, but I referred to a button for about:addons, as well. The linked script has just to be adapted. |
Beta Was this translation helpful? Give feedback.
-
So the about:config scripts need to be adapted for about:addons? Are there any plans for this? Are you suggesting I continue my conversation over there? |
Beta Was this translation helpful? Give feedback.
-
Yes, as is written in the beginning of the linked script.
Yes, if you still think you need this. |
Beta Was this translation helpful? Give feedback.
-
I tried to edit about_button.uc.js following the instructions. I don't know what I did wrong. I posted over there. |
Beta Was this translation helpful? Give feedback.
-
|
… and the link is Aris-t2/CustomJSforFx#127. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Aris-t2, Firefox 128.6.0esr I use TABS BELOW MAIN CONTENT (TABS ON BOTTOM), /css/tabs/tabs_below_main_content.css. |
Beta Was this translation helpful? Give feedback.
-
|
In black theme TAB with /css/tabs/default_tabs_reduce_height.css, is transparent. |
Beta Was this translation helpful? Give feedback.
-
|
Make sure you are using |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to move the "Zoom" entry to the top of the menu
|
Beta Was this translation helpful? Give feedback.
-
|
You better should have mentioned that this is the main panel menu. Add this to your #appMenu-zoom-controls {
order: -1 !important
}If you want to re-order more items (including separators) it gets more difficult – or at least effortful. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! You mention the main panel menu. I thought the image was self explanatory. For future reference, where else could I have been referring to? |
Beta Was this translation helpful? Give feedback.
-
|
I actually did not think of the fact that Aris explicitly asks for screenshots, but in general I consider it better behaviour also mentioning the area of the request in the text. It’s, for instance, possible that the image could not be loaded. For me: I do not use the panel menu very often and had to look first, whether it was this menu. Think of a situation, where the other side has to guess and is wrong in first or even second instance. This creates bad mood. |
Beta Was this translation helpful? Give feedback.
-
|
Just updated to FF 135. I am using a Windows HIGH CONTRAST THEME. The following DOES NOT OCCUR when not using HIGH CONTRAST mode. The FONT COLOR of the ACTIVE TAB is now 9EB874, a bland, pale grayish. It is now hard to read the tab. With FF135 it was BLACK. How do I get it back to BLACK? I have searched ALL the .css files, and nowhere therein do I find "9EB874". Nor is it a color I have defined for any of the HIGH CONTRAST colors. attached is my modified color_variables.css file, if that helps. |
Beta Was this translation helpful? Give feedback.
-
|
Is this color part of this project or does this also happen without any CSS files? |
Beta Was this translation helpful? Give feedback.
-
|
A. I went from FF 136.04 to 139.01 since first asking this question. B. The font color for INACTIVE TABS is also 0xFFFFF for cases 1 & 2 above. #TabsToolbar { So, basically, all I want to know is: how do I make the fonts for ALL the possible various tabs (active, inactive and what the others are) please excuse the lack of code formatting. the "add code" button wasn't working for me today. |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys: I'm using container tabs with tab text matching the container tab:
However, after updating to Firefox 135, when selecting a container tab, the tab text color switches from the container color to black:
Is there any way to revert back to the tab text being the same as the container color? |
Beta Was this translation helpful? Give feedback.
-
|
You are looking for this: .tabbrowser-tab[usercontextid] .tab-text {
color: var(--identity-icon-color) !important;
} |
Beta Was this translation helpful? Give feedback.
-
|
In Fx135 there has for addon buttons another level in the DOM – a box with class name I’ve for now added this style to my :root[uidensity="compact"] .unified-extensions-item-row-wrapper {
margin-inline: -2px !important
}May be there is a better way, but it works for me. Edit: toolbar .toolbaritem-combined-buttons > .unified-extensions-item-row-wrapper > .toolbarbutton-1 {
padding-inline: 0 !important;
} |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I will add this to next update. |
Beta Was this translation helpful? Give feedback.
-
|
I added the style above to the bottom of my userChrome.css but i'm still stuck with the same issue: Edit: Did a clean re-Installed of the code and it significantly improved. Added a few more options and am back to normal. Sorry for the false alarm. Thanks
|
Beta Was this translation helpful? Give feedback.
-
|
Just as first impression and reaction: In Fx 136 something has changed regarding the tab audio icons, so that the rules do not work anymore. There is still And: I have not noticed it yet, but there seems now to exist a Update: Oh, see in Camp Firefox (in German): message from 5 March 2025, 17:07 and answers from the same day. Apparently, some things are not possible anymore with userChrome.css alone. There is a rule suggestion I did not try myself yet, but is marked as most helpful answer: 5 March 2025, 19:11. |
Beta Was this translation helpful? Give feedback.
-
Not sure, if the translation of the above text is what Mozilla is using. Just hover the muted and unmuted icons an the correct text from your locale will appear. |
Beta Was this translation helpful? Give feedback.
-
|
Quoting myself:
Oh, this is easy, I meant easy – use .tab-audio-button {
--button-size-icon-small: 22px !important;
--button-min-height-small: 22px !important;
transform: transform: translateY(-3px);
} |
Beta Was this translation helpful? Give feedback.
-
|
I suggest to also use one of these two: /* hide the hover box/color */
.tab-audio-button {
--button-background-color-ghost-hover: transparent !important;
} /* border radius: --button-border-radius and border-radius */
.tab-audio-button {
--button-border-radius: 30px !important;
border-radius: 30px !important;
}(^^ If you want a round button in default and hover states.) |
Beta Was this translation helpful? Give feedback.
-
|
Thank you Aris-t2. I have done a mix of the two that you provided and added it to my overall audio code, which suits me. `/* Audio Icon with Sound */ /* Audio Icon when Muted */ /* Border radius and Background Colour on Hover */ |
Beta Was this translation helpful? Give feedback.
-
|
BTW, Aris:
Here I also added And for the button-border-radius (I’ve added a radial gradient as background-image, so I need this) I use And for what it’s worth, just as another example see my answer from 12 March 2025, 00:51 in Camp Firefox (so, with German text and comments). |
Beta Was this translation helpful? Give feedback.
-
|
Ohhh Welll, Firefox is striking again with elements & ID changes etc. I also came across in that German site (translated) this rule I am not understanding ::part(button) as in; Hopefully soon the God of this code, Aris-t2, will come out with an update to the two audio css files, along with my suggestion of |
Beta Was this translation helpful? Give feedback.
-
All these rules containing |
Beta Was this translation helpful? Give feedback.
-
|
Yep Right! Thank You. Read it and clear as mud for my very small css, non-java, capabilities. 😳 I'll leave that to you and Aris-t2 👨🎓😄 |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if this is a css thing |
Beta Was this translation helpful? Give feedback.
-
|
I hope Aris-t2 returns soon for an update. With the most recent Firefox update the default "out of the box" experience / interface continues to get worse. Lots of crushed or overlapping UI elements. |
Beta Was this translation helpful? Give feedback.
-
|
Dear USERS! Does anyone know how to change the color of the blue-cyan frame when I click inside the urlbar? (see pic) |
Beta Was this translation helpful? Give feedback.
-
|
There are two ways you can do it. The easier way is to change the value of the global variable that's responsible for the color of that outline. Note that this will also affect the color of the focus-outline that appears around the searchbar as well. Simply add the following to the list of color variables in config/color_variables.css --toolbar-field-focus-border-color: #ff0000 !important; /* Use your own color */The second way is if you specifically want to target the focused-outline around the urlbar without also affecting the outline around the searchbar. Simply add the following rule to your my_userContent.css #urlbar[focused]:not([suppress-focus-border]) > .urlbar-background {
outline-color: #ff0000 !important; /* Use your own color */
}Just to be thorough, if you prefer the 2nd method and you wanted to affect both the urlbar and searchbar, then you can also add the searchbar thusly: #urlbar[focused]:not([suppress-focus-border]) > .urlbar-background,
#searchbar:focus-within {
outline-color: #ff0000 !important; /* Use your own color */
} |
Beta Was this translation helpful? Give feedback.
-
|
My border around the URL is a shade of GREEN. I made no change about it to User Chrome I use a Windows HIGH-CONTRAST theme. |
Beta Was this translation helpful? Give feedback.
-
|
Your second method works great deedub-hub, but I noticed in the sidebar (History/Bookmarks), that the search field there is not affected. Any idea how we can add that one too? |
Beta Was this translation helpful? Give feedback.
-
As a preface to what I say below I should point out that, like many of us, I'm just a layman with a keen interest in learning, so I welcome any corrections from others who are more knowledgeable. As for the Bookmarks and History search fields in the sidebar, those input elements are encapsulated inside the shadow DOM. My understanding is that any CSS rules that you create in a userChrome stylesheet will have no effect on elements inside the shadow DOM. For example, the focus ring for the Bookmarks and History search fields gets its color from the global variable called --toolbar-field-focus-border-color. If you assign a new color value to that global variable, lots of elements will indeed inherit the color change, as can be seen when tabbing around the user interface. However, it won't work on the Bookmarks and History search fields in the sidebar, because those input elements are inside the shadow-root, and thus the inheritance from any CSS in the userChrome stylesheet is blocked. For the same reason, it will also not work if you try to target the input elements with the following rule: #main-window #sidebar-box[sidebarcommand="viewBookmarksSidebar"] #sidebar-search-container #search-box #input[type="search"]:focus,
#main-window #sidebar-box[sidebarcommand="viewHistorySidebar"] #sidebar .sidebar-panel .options-container moz-input-search #input[type="search"]:focus {
outline-color: #ff0000 !important;
}It was only this past week that I became acquainted with the shadow DOM and its restrictions. While doing a bit poking around online I've already seen glimpses of ways that the barrier of the shadow DOM can be pierced, but there is much to learn. |
Beta Was this translation helpful? Give feedback.
-
|
There is a divider line on my Bookmarks Toolbar at the end of the last Bookmark. How do I remove it? |
Beta Was this translation helpful? Give feedback.
-
delete it in Manage Bookmark |
Beta Was this translation helpful? Give feedback.
-
|
What? That doesn't make sense. |
Beta Was this translation helpful? Give feedback.
-
|
Delete it there Or you could technically delete it with right click but you have to click on the exact pixel of the line. |
Beta Was this translation helpful? Give feedback.
-
|
Oh What the hell is that? I've never seen that before. Yes I did have it |
Beta Was this translation helpful? Give feedback.
-
|
After updating to 146 I've got white on black menus and sidebar again; it is "because of my theme" but why has it happened again? This bug last happened in 140 https://bugzilla.mozilla.org/show_bug.cgi?id=1971487 and they fixed it, why's it back? Or is it something else? |
Beta Was this translation helpful? Give feedback.
-
|
I pray to the one and only true god, Aris, please come back and save us! |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe I'm too pessimistic but I frankly think it's time to fork this project, five months without any update from its creator don't bode well. |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone know if the creator is still even alive? Does he not have anything to say about this? |
Beta Was this translation helpful? Give feedback.
-
|
He is/was usually responsive within48 hours so I fear something is amiss. And he knows this all SO well I doubt anyone can totally fill his shoes.
On Dec 19, 2025, at 4:03 PM, Joe Petree ***@***.***> wrote:
Does anyone know if the creator is still even alive? Does he not have anything to say about this?
—
Reply to this email directly, view it on GitHub <#722 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJFPUUQS5HNFPI7WYW7UHD4CRRZ3AVCNFSM6AAAAABTZI6442VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMZQGIZDANI>.
You are receiving this because you commented.
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#722 (comment)", "url": "#722 (comment)", "name": "View Discussion" }, "description": "View this Discussion on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
|
Beta Was this translation helpful? Give feedback.
-
I would not recommend doing it, primarily because of security vulnerabilities. Disabling update checks and using an unpatched version will leave you exposed to known exploits. Just to name a few of the things you would be vulnerable to, there are zero-day threats, or access to sensitive data, such as form history auto-fill, resource timing API leaks, or local file reads via drag-and-drop and accessibility tools. There is also address bar spoofing with RTL characters or invalid protocols, same-origin policy violations. There is also bypassing of Content Security Policy (CSP), which is a web security standard that helps browsers enforce restrictions on content loading to mitigate attacks like cross-site scripting, or phishing, or privilege escalation. There are other execution flaws like integer overflows in data structures, regex parsing errors in PAC files, and sandbox escapes in XPCOM or JavaScript can execute malicious code without user interaction. In addition to security, there are other issues that wouldn't be addressed. Older versions miss optimizations for speed, JavaScript execution, and page loading. Updates enhance overall browser efficiency, reducing lag on modern websites. Without updates, compatibility problems with sites, extensions, and plugins persist, leading to crashes or freezes. You would also be forgoing privacy enhancements, tracking protection, and customization options introduced in new releases. Firefox evolves based on the latest web standards, which older builds ignore. Again, although it is possible to do, which would only take a 5-minute search to find out how, I would not advise anyone to prevent Firefox from checking for updates. If you do so, you do it at your own risk. |
Beta Was this translation helpful? Give feedback.
-
|
@cadeyrn Nonsense. Updates nowadays are garbage. Always ruining, removing stuff, why everything is getting more bloated. It's not just Firefox it seems to be widespread. Gone are the days when one could wait for updates with excitement. Nowadays it's anxiety or annoyance. @joefiesta You can't do it forever. After some time new standards and technology will break websites, and even before websites will actively sabotage your browser, and useragent faking only partly helps. |
Beta Was this translation helpful? Give feedback.
-
|
@mszo - You're 100% correct. I'm foolhardy wanting to never upgrade Firefox. And, I doubt I'll stop. I suspect long ago, it was an almost imdependent browser, written to get away from Microsoft's garbage (although it was not garbage back in the Win 98 and Win 7 days). Now, sadly, Mozilla is just another mega-corporation, trying to please whom? I don't know. The uncountable cosmetic changes made are totally absurd. Just the other day I heard someone--other than me!!!--complain about the new iPhone O/S 26.2. Same sort of unnecesarry cosmetic garbage--at least most of it. |
Beta Was this translation helpful? Give feedback.
-
|
@joefiesta Mozilla is far from a megacorporation, but sadly you can't tell it by looking at what they do with browser. |
Beta Was this translation helpful? Give feedback.
-
|
@mzso I had no idea. But, if that is the case, why do they change it so much? That is, why do they change it so much, when they don't seem to have adequate personnel to test or explore the implications of what they are changing? Do they think they need to keep changing it because people like change? (boy, if there are such people, they need help.) |
Beta Was this translation helpful? Give feedback.
-
|
I use Firefox ESR to extend the time of releases for me. Used to be two year, now a little more than one. Eventually, there will be something you want that will not run on that older version. So then I upgrade. Do note, this last to 146 was the FIRST time I did not need to do ANY CSS changes. First time ever for me.
Historically something would breakand Aris would lead me to what to change then good again for another year or more.
On Dec 21, 2025, at 3:57 PM, Dave Williamson ***@***.***> wrote:
https://www.perplexity.ai/search/can-you-force-firefox-to-never-NP_5r_eCRWeBH56jjTpX1g#0 <x-msg://1/url>
|
Beta Was this translation helpful? Give feedback.
-
|
Hello! Margin is already set to zero, so I don't know what causes this: .toolbaritem-combined-buttons{
height: 5px !important;*/
padding-block-start: 0px !important;
padding-block-end: 0px !important;
margin: 0 0px !important;
} |
Beta Was this translation helpful? Give feedback.
-
|
goodby message from Aris |
Beta Was this translation helpful? Give feedback.
-
|
This is very unfortunate, but understandable. I really hope someone else takes up the mantle and forks this. Personally, I only use it to make it look close to the classic firefox interface before the Australis UI update, so the v4 version, which means I get exactly what I want just by installing this package and using everything as default out of the box. It will be a shame to see it begin to decay. |
Beta Was this translation helpful? Give feedback.
-
|
@CrazieIvan Thanks for the heads up. It's not likely that I would've discovered the message from Aris otherwise. |
Beta Was this translation helpful? Give feedback.
-
|
I also almost missed it. I just happened to click on Aris's main page that shows the contributions tracker and noticed one green box from December... |
Beta Was this translation helpful? Give feedback.
-
|
I thought I would pass this along for anyone interested in styling a component of Firefox's UI that may or may not show itself very often. It's a notification bar that pops up, and you will likely remember having seen it upon first opening Firefox just after installing a new version. 
There are different messages that this same bar will display when triggered by other events, such as:
Since I plug my USB wireless modem into my laptop every day, I see this bar on a regular basis. By default the bar is a plain ugly white, so I created a couple of style rules to give it some color. You can target the bar with these selectors (as of Firefox version 147). A good place to put the code is in my_userChrome.css #main-window #notifications-toolbar notification-message {
background-color: #yourcolor !important;
}
/* This "vbox" is the parent container, so
giving it a darker color makes it look like
a border around the bar. */
#main-window #notifications-toolbar vbox {
background-color: #yourcolor !important;
}
/* This hides the decorative little color
gradient on the left side of the bar. */
#main-window #notifications-toolbar notification-message::before {
background-image: none !important;
}
A couple of notes about this bar: • Firefox only renders the bar programmatically when specific triggers occur (as I outlined above). As far as I'm aware there is no documented or reliable way to “spoof” the built‑in triggers in order to trick Firefox into deciding to show the bar on command. Those checks are internal and not exposed via any preferences, WebExtensions, or normal JavaScript APIs. Consequently, you would not be able to view the bar on demand to see the effect of the styles that you had applied to it. Of course you will eventually see the bar during such times as after installing a new version. • The innermost child elements of the bar, such as the message text and button, are isolated inside of the shadow DOM, so any style rules that you try to create for those parts of the bar will have no effect. |
Beta Was this translation helpful? Give feedback.
-
|
I have modified bookmark_icons_colorized.css. Please add the icon to the image folder. Please see the attached image for the changes. /* Firefox userChrome.css tweaks ********************************************************/
/* Github: https://github.com/aris-t2/customcssforfx ************************************/
/****************************************************************************************/
.folder-icon,
#editBMPanel_chooseFolderMenuItem :is(.menu-icon,.menu-iconic-icon),
treechildren::-moz-tree-image(title, container),
treechildren::-moz-tree-image(title, query, hostContainer) {
list-style-image: url("./../../image/folder-item.png")!important;
}
treechildren::-moz-tree-image(title, open) {
list-style-image: url("./../../image/folder-item2.png")!important;
}
treechildren::-moz-tree-image(title, container, livemark) {
list-style-image: url("./../../image/feedIcon16.png") !important;
}
#editBMPanel_folderMenuList:-moz-any([label="Bookmarks Toolbar"],[label="Lesezeichen-Symbolleiste"]) .menulist-icon,
#editBMPanel_toolbarFolderItem :is(.menu-icon,.menu-iconic-icon),
treechildren::-moz-tree-image(container, OrganizerQuery_BookmarksToolbar),
treechildren::-moz-tree-image(container, queryFolder_toolbar_____) {
list-style-image: url("./../../image/bookmarksToolbar.png") !important;
}
#editBMPanel_folderMenuList:-moz-any([label="Bookmarks Menu"],[label="Lesezeichen-Menü"]) .menulist-icon,
#editBMPanel_bmRootItem :is(.menu-icon,.menu-iconic-icon),
treechildren::-moz-tree-image(container, OrganizerQuery_BookmarksMenu),
treechildren::-moz-tree-image(container, queryFolder_menu________) {
list-style-image: url("./../../image/bookmarksMenu.png") !important;
}
#editBMPanel_folderMenuList:-moz-any([label="Other Bookmarks"],[label="Weitere Lesezeichen"]) .menulist-icon,
#editBMPanel_unfiledRootItem :is(.menu-icon,.menu-iconic-icon),
treechildren::-moz-tree-image(container, OrganizerQuery_UnfiledBookmarks),
treechildren::-moz-tree-image(container, queryFolder_unfiled_____) {
list-style-image: url("./../../image/unsortedBookmarks.png") !important;
}
treechildren::-moz-tree-image(title, query),
treechildren::-moz-tree-image(query) {
list-style-image: url("./../../image/folder-item.png") !important;
}
treechildren::-moz-tree-image(title, query, dayContainer) {
list-style-image: url("./../../image/calendar.png") !important;
}
treechildren::-moz-tree-image(query, OrganizerQuery_History),
treechildren::-moz-tree-image(query, OrganizerQuery_history____v) {
list-style-image: url("./../../image/history-XP.png") !important;
}
treechildren::-moz-tree-image(query, OrganizerQuery_allbms_____v) {
list-style-image: url("./../../image/Fx56-allBookmarks.png") !important;
}
treechildren::-moz-tree-image(query, OrganizerQuery_downloads__v) {
list-style-image: url("./../../image/downloads.png") !important;
}
toolbarbutton.bookmark-item[container],
.bookmark-item[container] .menu-iconic-left :is(.menu-icon,.menu-iconic-icon) {
list-style-image: url("./../../image/folder-item.png") !important;
}
toolbarbutton.bookmark-item[container][open],
.bookmark-item[container][open] .menu-iconic-left :is(.menu-icon,.menu-iconic-icon) {
list-style-image: url("./../../image/folder-item2.png")!important;
}
.bookmark-item[container][livemark] {
list-style-image: url("./../../image/livemark-folder.png") !important;
}
.bookmark-item[container][livemark] .bookmark-item {
list-style-image: url("./../../image/livemark-item.png") !important;
}
.bookmark-item[container][livemark] .bookmark-item[visited] {
list-style-image: url("./../../image/livemark-item2.png") !important;
}
.bookmark-item[container][query],
.bookmark-item[container][query][open],
.bookmark-item[container][query] > .menu-iconic-left > :is(.menu-icon,.menu-iconic-icon),
.bookmark-item[container][query][open] > .menu-iconic-left > :is(.menu-icon,.menu-iconic-icon) {
list-style-image: url("./../../image/query.png") !important;
}
treechildren::-moz-tree-image(title, query, tagContainer),
treechildren::-moz-tree-image(query, OrganizerQuery_tags_______v),
.bookmark-item[query][tagContainer] {
list-style-image: url("./../../image/tag.png") !important;
}
.bookmark-item[query][dayContainer] {
list-style-image: url("./../../image/calendar.png") !important;
}
.bookmark-item[query][hostContainer] {
list-style-image: url("./../../image/folder-item.png") !important;
}
.bookmark-item[query][hostContainer][open] {
list-style-image: url("./../../image/folder-item2.png") !important;
}
/* Bookmarks roots menu-items */
#subscribeToPageMenuitem:not([disabled]),
#subscribeToPageMenupopup {
list-style-image: url("./../../image/feedIcon16.png") !important;
}
/*** Fx143 ***/
#bookmarksToolbarFolderMenu > :is(.menu-icon,.menu-iconic-icon),
#BMB_bookmarksToolbar > :is(.menu-icon,.menu-iconic-icon),
#editBMPanel_toolbarFolderItem > :is(.menu-icon, .toolbarbutton-icon) {
content: url("./../../image/bookmarksToolbar.png") !important;
}
#menu_unsortedBookmarks > :is(.menu-icon,.menu-iconic-icon),
#BMB_unsortedBookmarks > :is(.menu-icon,.menu-iconic-icon),
#editBMPanel_unfiledRootItem > :is(.menu-icon,.menu-iconic-icon) {
content: url("./../../image/unsortedBookmarks.png") !important;
}
#editBMPanel_folderMenuList[selectedGuid="unfiled_____"] {
list-style-image: url("./../../image/unsortedBookmarks.png") !important;
}
#editBMPanel_folderMenuList[selectedGuid="toolbar_____"] {
list-style-image: url("./../../image/bookmarksToolbar.png") !important;
}
#editBMPanel_folderMenuList[selectedGuid="menu________"] {
list-style-image: url("./../../image/bookmarksMenu.png") !important;
}
.bookmark-item[container] > :is(.menu-icon, .toolbarbutton-icon),
.folder-icon > :is(.menu-icon, .toolbarbutton-icon) {
content: url("./../../image/folder-item.png") !important;
}
#editBMPanel_bmRootItem > :is(.menu-icon, .toolbarbutton-icon) {
content: url("./../../image/bookmarksMenu.png") !important;
}
/* "Other Bookmarks" folder in the Bookmarks Toolbar */
#OtherBookmarks > :is(.menu-icon, .toolbarbutton-icon) {
content: url("./../../image/unsortedBookmarks.png") !important;
}
/********************************************************************************************/
/* ::::: Change the >v displayed in the tree in the sidebar to ▼△ ::::: */
treechildren::-moz-tree-twisty {
list-style-image: url("./../../image/twisty-clsd-aero.png") !important;
margin-right: -0.3em !important;
margin-top: 0.0em !important;
}
treechildren::-moz-tree-twisty(open) {
list-style-image: url("./../../image/twisty-open-aero.png") !important;
margin-right: -0.3em !important;
margin-top: 0.0em !important;
}
treechildren::-moz-tree-twisty(hover) {
list-style-image: url("./../../image/twisty-clsd-hover-aero.png") !important;
margin-right: -0.3em !important;
margin-top: 0.0em !important;
}
treechildren::-moz-tree-twisty(hover, open) {
list-style-image: url("./../../image/twisty-open-hover-aero.png") !important;
margin-right: -0.3em !important;
margin-top: 0.0em !important;
}
/********************************************************************************************/
/* ::::: Change the >v displayed in the tree in the sidebar to + - ::::: */
/*treechildren::-moz-tree-twisty {
list-style-image: url("./../../image/twisty-clsd.png") !important;
margin-right: -0.3em !important;
margin-top: 0.0em !important;
}
treechildren::-moz-tree-twisty(open) {
list-style-image: url("./../../image/twisty-open.png") !important;
margin-right: -0.3em !important;
margin-top: 0.0em !important;
}
*/
/* ::::: Dotted line folder tree in sidebar ::::: */
/*treechildren::-moz-tree-line {
visibility: visible !important;
border: 1px dotted #999 !important;
}
*/
/* ::::: tree separator. Separator when folder tree is dotted line ::::: */
/*treechildren::-moz-tree-separator {
border-bottom: 1px solid ThreeDShadow !important;
margin-top: 1px !important;
margin-left: 1px !important;
margin-right: 0px !important;
}
*/
/********************************************************************************************/
/* ::::: tree rows ::::: */
/*treechildren::-moz-tree-row {
min-height: 2.0em !important;
border-width: 1px !important;
}
#places treechildren::-moz-tree-row {
min-height: 2.0em !important;
border-width: 1px !important;
}
treechildren::-moz-tree-indentation {
width: 1.4em !important;
}
*/ |
Beta Was this translation helpful? Give feedback.
-
|
twisty + - |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Make sure you have updated your configuration to the most recent version of this projects files and are using the latest version of the "options" required by your Firefox version >before< reporting problems!
Continued from #3, #41, #88, #109, #133, #163, #189, #211, #241, #273, #308, #368, #404, #417, #454 and #606
Instead of opening new "issues" for general talk we can use this area for discussions, feedback and questions. Open new "issues" for real bugs and problems.
Custom JS scripts to restore more classic features
https://github.com/Aris-t2/CustomJSforFx
Things this project will not target/recreate
Things not possible with CSS
Beta Was this translation helpful? Give feedback.
All reactions