Probably not intentional, but every site's theme just turned a(n admittedly nice) shade of blue.
CGCC:
Infosec:
Cooking:
]
Worldbuilding:
asked Apr 13, 2022 at 18:23
-
12Not intentional! We just now shipped a change using CSS custom properties more widely and seems you caught a bug. We'll have a fix out shortly.– Dan Cormier StaffCommented Apr 13, 2022 at 18:31
-
3And dark mode on SO looks awful (very dull). @Dan, Is this caused by the same thing or was that intentional?– 41686d6564Commented Apr 13, 2022 at 18:36
-
I find this blue color hard to read actually. Best is blackish text on white background.– NasserCommented Apr 13, 2022 at 18:58
-
@Nasser It's an unintentional change (see Dan Cormier's comment), they'll be changing it back to the way it was before soon (status-planned).– Radvylf ProgramsCommented Apr 13, 2022 at 19:01
-
3We have a fix building out as we speak. It'll arrive on production soon– Ben Kelly StaffModCommented Apr 13, 2022 at 19:03
-
@BenKelly Is this also why the avec-serif fonts have all switched to sans-serif (e.g. on Physics)?– robCommented Apr 13, 2022 at 19:06
-
1@rob Yep! I'll post details in the answer once the fix is verified to be in place– Ben Kelly StaffModCommented Apr 13, 2022 at 19:08
-
I was planning on upvoting this for the recognition of the change, but I don't agree that it's admittedly nice. It's hard on the eyes, in my opinion.– ggorlenCommented Apr 13, 2022 at 19:18
-
@ggorlen It was mostly a joke, it could be much worse colors.– Radvylf ProgramsCommented Apr 13, 2022 at 19:19
-
3Glad it turned out to be a bug rather than a feature. It's hard to tell sometimes.– ggorlenCommented Apr 13, 2022 at 19:22
-
@ggorlen it is only April, 1st once a year. ...– reneCommented Apr 13, 2022 at 20:38
Add a comment
|
1 Answer
This issue has been fixed. Short version: There was an upstream change in our Stacks library that caused the css specificity of the default theme to be higher than the network themes. As a result, the default theme was applied to all of the components (buttons, fonts, and so on) across the network. We put in a quick (but reliable) fix on the Stack Exchange-side of things while we look into addressing the root cause in Stacks.
answered Apr 13, 2022 at 19:18
-
13Does the SE test environment have an upstream "test" Stacks file where changes should roll to first, before that file is moved to production? If not, adding that process would help catch bugs like these because you'd notice it right away in the SE test site environment.– TylerHCommented Apr 13, 2022 at 19:29