thanks jscher2000 ¡¡¡

it is now ok ¡¡¡ When you insert it, is necessary wait a little time. And then, ok

And the other firefox users? Do they have the same problem?

Lombard.Lombard said

And the other firefox users? Do they have the same problem?

Which problem? Obviously everyone has gray folders, if that's what you mean.

Yes, It´s. Is the first time I saw it in firefox. If it is not a problem, it is not normal. I dont understand the reason, I dont understand why. is it normal? gray folders?.

This is all part of a redesign (Photon) to speed up Firefox as much as possible and reduce the memory usage. Gray SVG images are small and fast and do not need to be decompressed like compressed PNG images.

• https://www.ghacks.net/?s=photon

But, for the same reason, all firefox could be grey. I think it at users will not like it. I dont like it. Do you like it? Ok, thanks for the answer

Grey usually means that something, e.g. a folder, is unavailable.

Presumably, Firefox's developers didn't know this and, now they do, will quickly correct the issue.

I see, too, that there will be various shades of grey, presumably 50.

Providing fixes to issues where updates are objectionable to users is all very well, but is not the answer. Mozilla's developers must realise that Firefox is now widely used by the non-computer expert general public and not just by techno geeks

Hi fedup101, support volunteers can't make changes to Firefox. To submit suggestions for new or changed features, may I suggest:

• Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/
• Facebook: https://www.facebook.com/Firefox
• Reddit: https://www.reddit.com/r/firefox/
• Twitter: https://twitter.com/firefox

I tkink it has solution. If the user can change the color in the menu. So, if you want it grey, ok. But if you want it with colors, ok. The user chooses it.

cor-el said

This is all part of a redesign (Photon) to speed up Firefox as much as possible and reduce the memory usage. Gray SVG images are small and fast and do not need to be decompressed like compressed PNG images.

• https://www.ghacks.net/?s=photon

cor-el said

This is all part of a redesign (Photon) to speed up Firefox as much as possible and reduce the memory usage. Gray SVG images are small and fast and do not need to be decompressed like compressed PNG images.

• https://www.ghacks.net/?s=photon

If Firefox developers are having to go for grey folders to help reduce memory usage, it suggests that Firefox needs a serious look at to reduce a lot of unnecessary clutter or inefficient coding.

As I have said before on this forum, many, maybe most, users of Firefox want a safe and secure and fast browser which allows them to do a basic set of operations, which do not include downloading/watching TV or films for example. Maybe the developers who use all the functions in Firefox believe they are the norm, but they aren't. We've seen this same thing in mobile 'phone technology, 'phones that can do lots of things but which are when it comes to it used only for very few of them.

jscher2000 said

Hi fedup101, support volunteers can't make changes to Firefox. To submit suggestions for new or changed features, may I suggest:

• Feedback: https://qsurvey.mozilla.com/s3/FirefoxInput/
• Facebook: https://www.facebook.com/Firefox
• Reddit: https://www.reddit.com/r/firefox/
• Twitter: https://twitter.com/firefox

I wasn't actually making suggestions, only joining in a thread . Bearing in mind that from previous correspondence on this forum, it seems that Firefox developers rarely if ever look at it, I very much doubt that any notice would be taken of an everyday Firefox user on any of those links, although I will try the feedback link, but only expect the usual blah about your feedback is important to us, we want Firefox to be the world's leader in web browsing etc., etc, etc..

I think that the problem with Mozilla/Firefox is that it is now just another, self-perpetuating organisation where change MUST take place, irrespective of any adverse effect on users, so that the organisation can justify and maintain its existence.

This is a variation that also modifies colors on the Bookmarks Toolbar and in the menu that drops from the Bookmarks Menu button on the toolbar (if you add that button in Firefox 57+):

/* Colored bookmark sidebar, toolbar, menu button containers */
  /* Standard folder */
  #bookmarks-view treechildren::-moz-tree-image(container),
  #PlacesToolbarItems toolbarbutton[container="true"] .toolbarbutton-icon,
  #PlacesToolbarItems menu[container="true"] .menu-iconic-left,
  #BMB_bookmarksPopup menu[container="true"] .menu-iconic-icon {
    fill: gold !important;
  }
  /* Live Bookmark (RSS Feed) */
  #bookmarks-view treechildren::-moz-tree-image(container, livemark),
  #PlacesToolbarItems toolbarbutton[container="true"][livemark="true"] .toolbarbutton-icon,
  #PlacesToolbarItems menu[container="true"][livemark="true"] .menu-iconic-left,
  #BMB_bookmarksPopup menu[container="true"][livemark="true"] .menu-iconic-icon {
    fill: orange !important;
  }
  /* Smart bookmark folder */
  #bookmarks-view treechildren::-moz-tree-image(container, query),
  #PlacesToolbarItems toolbarbutton[container="true"][query="true"] .toolbarbutton-icon,
  #PlacesToolbarItems menu[container="true"][query="true"] .menu-iconic-left,
  #BMB_bookmarksPopup menu[container="true"][query="true"] .menu-iconic-icon {
    fill: dimgray !important;
  }
  /* These "containers" are SVG in the sidebar, not yet on the menu */
  #bookmarks-view treechildren::-moz-tree-image(container, OrganizerQuery_BookmarksMenu) {
    fill: olive !important;
  }
  #bookmarks-view treechildren::-moz-tree-image(container, OrganizerQuery_BookmarksToolbar) {
    fill: olive !important;
  }
  #bookmarks-view treechildren::-moz-tree-image(container, OrganizerQuery_UnfiledBookmarks) {
    fill: olive !important;
  }

LATEST VERSION HERE: https://www.userchrome.org/what-is-userchrome-css.html#colorbookmarkfolder

Tonnes said

I’ve been fiddling a bit with some CSS code (also to be found on the net somewhere else) and the following appears to be rather satisfactory so far. The code simply fills and modifies colors for the changed and mainly affected Bookmarks related folder icons in the Firefox 56 Sidebar and Library, as well as the Bookmarks Toolbar items in upcoming 57.

1. Click the menu button , click help (or press Alt, choose Help in the menu bar) and select Troubleshooting Information. You will be taken to a page with the address about:support (you could enter that in the address bar instead.)
2. Click Open Folder or Show in Finder or Open Directory (Win/Mac/Linux). This is the Profile folder.
3. If it isn’t there yet, create a subfolder called chrome.
4. Go into that folder and create a new text file called userChrome.css if it isn’t there yet.
5. Copy and paste the following code into the userChrome.css file (or add it if already present, except for the first line), save the file and restart Firefox.

@namespace url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul); .bookmark-item[container], treechildren::-moz-tree-image(container) { fill: gold !important; }
treechildren::-moz-tree-image(container, OrganizerQuery_BookmarksToolbar) { fill: black !important; }
treechildren::-moz-tree-image(container, OrganizerQuery_BookmarksMenu) { fill: black !important; }
treechildren::-moz-tree-image(container, OrganizerQuery_UnfiledBookmarks) { fill: black !important; }
treechildren::-moz-tree-image(container, livemark) { fill: orange !important; }
.bookmark-item[container][query],
treechildren::-moz-tree-image(container, query) { fill: dimgray !important; } (Note that when pasting, some empty lines one may see (1, 6, 8, 11, ...) can be omitted - some breaks were added just for formatting/readability in this forum.) Although the colors will not be 100% similar to what is used up to 55, they are easy to customize (see here for allowed colors), which may be needed for black/gray items when changing to a dark theme (more relevant to 57.) It actually works quite well for me in both 56 and 57 and offers more customization for the affected items than possible by default in pre 56 versions, since some items can have their own color specified. The code may not be perfect and/or could be improved - there will probably be various ways to set this up - and of course I could edit the post if there is something really bad in there. It should however be a nice and easy start for those who want it so badly, and can be set up within a minute. Use at your own risk, though nothing should be able to break Firefox. Hope this helps. _{/Edit: small markup fix at the bottom}

That did absolutely nothing! UGH

King Ray said

That did absolutely nothing! UGH

You probably did something wrong then. _{(Also, please don’t needlessly quote.)}

Tonnes said

King Ray said

That did absolutely nothing! UGH

You probably did something wrong then. _{(Also, please don’t needlessly quote.)}

Like what? I just copied & pasted. What is unclear is what comprises the first line that shouldn't be included in the file. I don't remember a lot about my HTML days. So, what is the first keyword that should be in that file?

This thread provided a basic answer for modifying the style/colors for v56 (and 57+) around that time and was considered as providing a solution. Subsequent replies and questions provided links to pages containing modified versions or variations, including the script found on userchrome.org that is somewhat similar to or another variation of the script provided by jscher2000 above. Personally I would say there is little to no use filling up the thread with additional questions such as why the file does not work for some - it just should - as well as providing negative feedback about the change (by others, not you.) Yet it could be left open for issues with regard to why the script should not work at all, and as you can see, this thread is still referred to as a discussion by userchrome.org.

The @namespace line is what you probably referred to, though it is actually no longer needed - the quoted script should also work without it (verified on Win 7 32-bit, but I haven’t seen reports of the original script not working for 64-bit versions or other OSes.) If it doesn’t, either with or without the line, make sure the file has the proper name and location, to restart Firefox, to not hide known file types, and that you do not start Firefox in Safe mode. Also see this question’s reply for finding out if the file is actually loaded. If you can find a new culprit, I’d be happy to hear it and modify the original version/reply.

Hope this helps.

Hi King Ray, I created a downloadable file as a shortcut. See:

https://www.userchrome.org/what-is-userchrome-css.html#colorbookmarkfolder

You either can rename that to userChrome.css or, if you already have a userChrome.css file you want to preserve, copy/paste its contents into your file.

If you did not already create the chrome folder, see Steps #1-3 here: https://www.userchrome.org/how-create-userchrome-css.html

I previously used the Classic Theme Restorer add-on. The developer of this add-on is now offering a userChrome.CSS file that recreates most of that functionality. It doesn't have everything that I would like and it's not tweakable (unless you want to mess with the CSS) but it's got most of what I want. He makes it very easy to download and install the fix. He's putting out updates periodically. http://techdows.com/2017/09/classic-theme-restorer-userchrome-css-modify-firefox-57-photon-ui.html

Because I see many emails about this subject, I can't find the one that solved the problem, but it wasn't in this thread. Problem was the location of that file. I followed a link that said how to open the profile folder (through Help, Troubleshooting Information, etc.) and I put the file there. That's not where it was supposed to go. So, I moved it using Windows Explorer, after following the screen-print of the actual location in another thread, and it worked.

Good to hear, but can you be more specific?

2. Click Open Folder or Show in Finder or Open Directory (Win/Mac/Linux). This is the Profile folder.
3. If it isn’t there yet, create a subfolder called chrome.

Unless you are using a Mac (or read the instructions on one even though you are on Windows), you should land in the profile folder, and this is where the (new) chrome folder should be, so I don’t see an issue there for Windows and Linux.

Mac users however land in the profile’s parent folder containing the actual profile folder(s) and additionally need to go into the active profile folder itself. Is that the addition you would like to see here (step 2), or perhaps in the Profiles article?