2
librewolf not loading css file (lemmy.world)
submitted 2 months ago by to c/FirefoxCSS@fedia.io
8 comments fedilink hide all child comments
 

i have used this same file before and same browser but its not loading. i checked settings in librewolf to make sure i had css enabled. but it still wont load.
i have file located at ~/.config/librewolf/librewolf/12345. default-default/chrome/userchrome.css

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 months ago (7 children)

The file has to be called userChrome.css, with a capital C.

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] 1 point 2 months ago* (last edited 2 months ago) (1 child)

    Using a capital 'C' in 'userChrome.css' and userContent.css file names is a longstanding convention... but not a requirement.

    Edit: CSS userChrome modifications work normally in Firefox on Windows OS' with a small 'c' in the 'userchrome.css' file name... unable to test if this also applies for macOS and Linux installations.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 months ago

    Are you on Windows? On Windows, filename capitalization in general does not matter.
    But OP seems to be on Linux. I just tried it on Linux with the filename as "userchrome.css" and it was not loaded.

    I would've been very surprised, if it did work on Linux, macOS etc., because to my knowledge, as a software engineer, there is no way to implement that without a second filesystem access, which would've delayed startup.
    Nowadays, you even have to set a about:config flag, specifically because they don't even want the first filesystem access to try to load the file...

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 1 point 2 months ago (4 children)

    It is. The above is a typo. I suffer from a condition called Hamhands.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 2 months ago (3 children)

    Hmm, not a lot to go off of then.

    Can you just go through these steps to see if anything isn't set up correctly?
    https://www.userchrome.org/how-create-userchrome-css.html

    You can also check via the Browser Toolbox, whether the file gets loaded.
    In the "Style Editor" tab, you can filter the list on the left and if "userChrome.css" isn't listed there, then it didn't get loaded.

    If it is listed in the Style Editor, then something about your rules is broken. You might be missing !important in places.
    Or your CSS rules might not target the right classes/ids/variables anymore. For example, I had a breakage about a month ago, because they renamed the CSS variable --toolbarbutton-inner-padding to --toolbarbutton-padding-inner.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 2 points 2 months ago (2 children)

    I will check this out when i get a chance! Thanks!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 months ago (1 child)

    Not using LW, but in FF there's an about.config. item called 'toolkit.legacyUserProfileCustomizations.stylesheets' that has to manually turned to 'true' to work.

    I don't like the FF setup (userChrome levels buried deep in the .mozilla folder), must be nice to have it handier like that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •