Yes, some styling has changed, a lot of it actually. No, the userChrome.css is not being ignored, as some settings do work. My guess (just mine, I'm not a decision-maker) is that this will evolve over time. I also had many settings that do not work for now.

No, the userChrome.css is not being ignored

Given the explicit context, I think "ignored" is a fair way to put it.

As you say though, technically it's not the userChrome: 115 also ignores the colors set by the user through the UI, or anywhere else that I can find so far. (Good thing nobody has any accessibility issues with colors ever, right?)

It looks like it might get fixed someday though: several other color bugs have been already.

Technically, in explicit context, the CSS is not being ignored. The problem is that the CSS code as written doesn't fit anymore. Since 115 has been released, several authors have shared CSS that works in 115 and that collection will continue to expand, but finding it will always be a search, as there has never been official support for CSS modifications. Several new CSS mods for color have surfaced here on the forum and this continues to be the place to find them. Like you, I have been watching and picking up bits and pieces of new CSS to replace what I used in 102.

You give me too much credit: I'm far too lazy to maintain a pile of CSS on a regular basis.  :)

I just stopped by because 115 doesn't even use the colors that are in the *menus* for its actual colors. Not "semi-unsupported hacks": basic functionality, and that seemed a fairly absurd oversight for even a .0 release, let alone a .3, so I thought I had to be missing something. Since it's just outright broken right now though, I'm going to choose the better part of valor and revert to 102 until either it isn't or some Kind Hero - such as yourself :P - manages to collect enough MacGuffins to sort it out that way instead.

Incidentally, as it may come in handy at some point: there are a *lot* of color vars in about:config. None of them fix the Folder or Message panes (unless I missed some), but there may be some cases where they're useful enough that they can avoid needing more CSS (i.e. could be set in a deployable prefs.js or somesuch, or at least be easier for normal users to deal with).

Best of luck on the quest.  :)

It's a valid point. Postbox is similar to Thunderbird and offers an infinite capability for color settings. That has never been a focus of Mozilla's.

I had a similar problem: my requirements weren't exactly the same as yours, but fairly similar.

Trying to translate my solution to your situation, you could try something like this:

   tr[is="thread-row"][data-properties~="new"] {
      color: #34ebdc !important;
      font-weight: normal;
   }

   tr[is="thread-row"][data-properties~="unread"] {
      color: #34c6eb !important;
      font-weight: normal !important;
   }

Not sure this is the best way to do it, but (something similar to) this worked for me, so fingers crossed it will help.

Hot damn! That works! Thanks pg_78! Nice work!

Using this css file by adding pg78 solution to my zebra stripe code that has never worked on one laptop yields unread new messages showing as blue.

/* ####### */ @namespace html url("http://www.w3.org/1999/xhtml");

1. threadTree tr:nth-child(2n) {

 background-image: linear-gradient(rgba(150,145,220,.325), rgba(0,0,0,.08)) !important;  

}

tr[is="thread-row"][data-properties~="new"] {
     color: #34ebdc !important;
     font-weight: normal;
  }
  tr[is="thread-row"][data-properties~="unread"] {
     color: #34c6eb !important;
     font-weight: normal !important;
  }

So something is working just a mystery at this point why zebra stripes not working on this one laptop. I have the code for that working on other computers.

FWIW - the namespace has changed, if I see this right. it is not XUL anymore, but html!

@namespace html url("http://www.w3.org/1999/xhtml");

If your userChrome stopped working, you should check that first.