-101

November 21, 2023: To help with internal managing issues, you may see a reference number added next to the status tag on your post. These numbers don't determine the order or priority of issues but will make it easier for internal staff to log and track progress.



October 26th, 2023

Thank you for all the bug reports, feedback, and concerns with this latest update. We have rolled out a handful of fixes based on those and are requesting more feedback on the new post regarding those.


It has been a long journey, but the time has come to finally bring our new colors to production! This post will serve three purposes:

  • The first is to announce the launch of said colors and celebrate with the community who helped us get here.
  • The second is to explain what we changed from our last post.
  • The third is to provide a space to report bugs.

Our new standards

Our goal is still the same: we want to be more accessible without hindering usability and setting standards to ensure we reduce inconsistencies across our sites.

As discussed before, we used APCA to guide our decisions. While we weren’t able to hit lightness contrast (Lc) value of 75 for all text, our large blocks of text do hit this and the rest of our text (with the exception of muted/disabled copy) will have an Lc value of at least 60.

At a high level, our light mode won’t feel that much different, but we believe that our dark mode has come a long way and that is thanks to the advice of a community member. Simply put, WCAG uses a simple contrast calculation that can not adjust for the human nonlinear perception and by using APCA our readability should improve for all users.

We’ve put much more detailed usage guidelines into our design system that discuss color usage, layering, emphasis levels, interaction states, and accessibility standards. We may not be meeting all of our own, new standards yet, but something we are aiming to do over time.

Changes from our last post

From the last meta post, we made the following changes based on your feedback:

  • Desaturated the blues and greens in light mode
  • Changed the hue of green in all modes
  • Darkened and desaturated the yellow in all modes
  • Did an overhaul of the “background” colors in dark mode to more seamlessly blend with their foreground brethren.

Once we got in and started examining the sites we made even more changes. We noticed that there were certain scenarios where our dark mode blue wasn’t passing and had to make adjustments. We also still struggled with our brand color, orange, and had to make the sacrifice to no longer use it in the UI.

We added in a purple color so designers could have the unique color to use for new features and onboarding

New Purple Palette

UI changes of note

The biggest change you’ll notice is the changes to the moderator and required tags. The moderator tags have changed from red to orange so they look less like an error state.

Then: Red moderator tags with red borders

Now: Orange moderator tags with orange borders

The required tags have changed from grey to a bold emphasis level of the site’s themed color. These tags were almost identical to muted tags, which we found to be a source of confusion.

Then: Grey required tags with grey borders

Now: dark blue required tags

Another change you will notice is that our toggles, radios, and checkboxes selecting component (dot/checkmark) will now switch to black instead of staying white in dark mode.

list of checkbox and radio elements in various states

Lastly, we had to lighten the meta theme a little to account for the new way we will do hover states. This will affect all meta sites themed with the black meta color.

Then: Black button with the word button in white

Now: Dark grey button with the word button in white

Next steps

This was a big effort for just a handful of folks so if you find bugs, please use this post to log them and we’ll add them to our backlog. We hope to iterate on this in the future, thinking of things like font size and ensuring we use more than just color to represent information. We appreciate your patience and help as we’ve worked through this. We hope you feel it’s as successful as we do.

46
  • 58
    Does this bring dark mode closer to being available on other sites than SO as well?
    – Mast
    Oct 19, 2023 at 18:33
  • 11
    Should site-specific bugs be reported here, or on per-site meta? Oct 19, 2023 at 18:42
  • 12
    @Mast From our developer... "Yeah, it gets us closer (particularly when it comes to custom themes having sufficient contrast), but we still got a ways to go to ensure a given site’s overrides play nice"
    – Piper Staff
    Oct 19, 2023 at 19:13
  • 54
    Wow, so many bugs reported (some of them blatant) in less than 2 hours. Was this really tested before launching?
    – hkotsubo
    Oct 19, 2023 at 19:34
  • 44
    @hkotsubo Nearly 10k lines of code added, 10k removed, 113 files effected across SE Network, SO sites, Enterprise sites, and Teams tested by 3 designers, 4 developers. Yes, we tried our best to test every corner, but we clearly missed some.
    – Piper Staff
    Oct 19, 2023 at 20:01
  • 76
    10k of lines added, 10k removed and 113 files affected just to change some colors and css stuff? Holy moly! Oct 19, 2023 at 20:29
  • 47
    It just looks so washed out in SO dark mode, it's lost the vibrant colours that made important parts stand out. Did this really get reviewed or did the designers forget about dark mode again?
    – Phil
    Oct 19, 2023 at 21:33
  • 24
    i genuinely thought that my not-normal monitor i'm on right now was the reason the colors in dark mode looked so strange (and not in a good way). starting fiddling with monitor settings for a minute before I saw the post on this... Oct 19, 2023 at 22:00
  • 45
    @Piper Yeah, that's a lot of work, but seriously, didn't anybody try to simply access the homepage in dark mode? Or check the colors of vote buttons? Looking at the bugs reported, many - if not all - of them seem to be basic stuff of the most accessed parts of the site, not hidden things in some obscure page. I don't mean to be rude and tell you how to do your job, but if the change is so big, perhaps you should've done a more comprehensive and careful test.
    – hkotsubo
    Oct 20, 2023 at 0:55
  • 13
    The issues here and in many other changes the team has made to the colors seem like the sort of thing that would be addressed by automated screenshot testing. A human would need to approve the changes, which they would do after verifying that the change is what they expect. For something like this, that'd be a lot to review, but then, it's a large change, and that time is time that doesn't have to be spent in repeated manual testing. It's unsurprising that with dozens of network sites with different themes, manual testing fails to catch stuff; that's where automation can lend a hand.
    – Ryan M
    Oct 20, 2023 at 1:10
  • 37
    I can't speak to accessibility, but the new colors are unpleasant and look washed out in dark mode. I kept thinking my laptop had gone into outdoor-light overbright washed out mode.
    – Andy Ray
    Oct 20, 2023 at 1:26
  • 25
    If you roll out such changes, you should have made an option to restore the previous state (or you should have done better job at testing!). For me personally StackOverflow is completely unusable now, both in light and dark mode. The high contrast toggle does nothing, everything is high contrast.
    – Chaosfire
    Oct 20, 2023 at 6:56
  • 30
    "tested by 3 designers, 4 developers" and not tested by single dedicated quality assurance team / person.
    – luk2302
    Oct 20, 2023 at 8:59
  • 23
  • 11
    We have heard the feedback on Dark Mode. I posted a separate answer addressing that. meta.stackexchange.com/questions/393939/new-colors-launched/…
    – Rosie StaffMod
    Oct 20, 2023 at 12:32

76 Answers 76

14

ref 459

Give us back the border for normal tags, as the background isn't rendered on high-contrast monitors

When a user's monitor is set to a high contrast level (such as if they want text to "pop out" more easily for accessibility, really light colors tend to blend into the background. This would happen with the current background color for normal (non-required, non-moderator-only) tags.

In the older style, there used to be a border around normal tags, but this seems to have been removed. Without it, on high-contrast monitors, the tags would appear as plain text rather than tags.

Can the border around normal tags please be added back?

4
  • 1
    I've added it to our backlog
    – Piper Staff
    Oct 19, 2023 at 19:01
  • 2
    @Piper Thanks! It would be really cool if you edited in status tags into each answer here with tags, on top of responding in the comments, so the status of them is clearer. Oct 19, 2023 at 19:03
  • @SonictheAnonymousHedgehog just for clarity: are you using the high contrast mode set in the Stack settings, an OS-level high contrast mode, or do you have a special monitor setting for high contrast? Or multiple/none of those? To get this one correct, it would be helpful to understand your circumstances a little better.
    – Dan Cormier Staff
    Oct 20, 2023 at 19:45
  • @DanCormier Monitor setting. On most desktop monitors if you dial the contrast all the way to 100 you'll see what I'm talking about. Oct 20, 2023 at 22:32
14

ref 474 and 476

The 404 pages are lighter grey than expected when using high-contrast dark mode, and are not consistent with other pages such as undeleted posts or the home page.

Image of 404 page with a lighter grey background than expected

And while we are at it the close and flag dialog are also this lighter grey even with high-contrast enabled. This is not very high contrast as I would expect with high-contrast mode:

Image of a low contrast flag dialog in high-contrast mode

3
  • The close panel is an issue in light mode as well.
    – wizzwizz4
    Oct 22, 2023 at 0:02
  • Thanks for reporting, the issue has been logged. Background adjustments will be made to get a 7:1 contrast ratio for HC mode for both the 404 page and the modals.
    – Carrott Staff
    Nov 20, 2023 at 23:48
  • @Carog Thank you.
    – CPlus
    Nov 20, 2023 at 23:49
14

"Looking for your Teams?" element isn't centered. (Maybe not new, but it stands out more to me now.) The screenshot is from Stack Overflow but the same is happening here.

enter image description here

3
14

The Help Center article 'How do I use tags to find topics I'm interested in?' still uses screenshots of the old design:

enter image description here

The screenshot of the article about inline tag-edits also uses the old design.

1
  • 4
    Thanks will flag this for us to update.
    – SpencerG StaffMod
    Oct 19, 2023 at 20:36
14

The relatively small color change makes my eyes have to work harder to read blue-on-blue:

old new
enter image description here enter image description here

I haven't checked, but it feels like the background and foreground colors are closer than before and it puts a strain on my eyes.

4
  • 6
    This is made worse by the name appearing twice due to the incorrect markup for the profile picture
    – Ryan M
    Oct 20, 2023 at 0:07
  • 1
    @RyanM Aha, is that was that is. I've been wondering about that :-)
    – Ted Lyngmo
    Oct 20, 2023 at 0:09
  • There was an update to our dark mode colors (more saturated) and the background of the usercard that should have helped with the contrast here. It looks much clearer on my monitor now (compared to the "new" screenshot you shared), so I'll mark this as completed. Let me know if that's not the case.
    – Carrott Staff
    Nov 21, 2023 at 20:54
  • 1
    @Carog Indeed! The colors are much better than they were when I posted this, thanks!
    – Ted Lyngmo
    Nov 21, 2023 at 21:15
14

People have already mentioned aspects of this, but the overall conclusion I draw is that

Yellow is not the new black.

It's awful for contrast, but it's not the greys that are the problem, it's the yellow.
Everywhere this yellow appears it's far too punchy. It's meant to be a gentle highlight, not
"Your attention is required right here, immediately!"

enter image description here

This one took some effort to screen-cap, the highlighted question you see on page refresh, but this is truly horrible.

enter image description here
Intentionally small, you don't need to read it.

I'm on a fully colour-calibrated machine here, I hate to think what this will look like on the usual consumer over-punchy laptop screen.

5
  • 4
    As far as the flash, a fix has been made in the source but hasn't been pushed out to production yet. Oct 20, 2023 at 8:54
  • 2
    That's good to hear - but it's everywhere this new yellowy-orange is used. It's just far too punchy.
    – Tetsujin
    Oct 20, 2023 at 8:56
  • Also reported by sonic-the-anonymous-hedgehog: meta.stackexchange.com/a/393980/387876
    – shaedrich
    Oct 20, 2023 at 21:35
  • These examples seem to be referring to our yellow, not orange so I've edited your post to reflect that. We did struggle a lot with finding the right balance between making the yellow color work with our contrast standards and still look "yellow". We have no plans to change the yellow color at this time.
    – Carrott Staff
    Nov 23, 2023 at 20:43
  • The yellow flash fix should be live now, the yellow background on watched posts was reduced to a lighter (less vibrant) stop as well and there's a fix for reducing the yellow background on Saves/Collection notes in the backlog. Hopefully this all helps remove some of the yellow prominence a bit. In regards to the community bulletin, it sounds like having it call more attention isn't such a bad thing.
    – Carrott Staff
    Nov 23, 2023 at 20:46
13

ref 484

Two buttons in the same header are two different blues. It may be that they have slightly different semantics but the color difference is too subtle to indicate that and rather just looks like an error.


enter image description here


The custom properties at question are

--_bu-filled-bg-selected  //rgb(21, 92, 162))

and

--_bu-filled-bg  //rgb(27, 117, 208)
1
  • Agree, the Watch/Unwatch button should be using the outlined class instead, an issue had been logged.
    – Carrott Staff
    Nov 21, 2023 at 21:04
13

Cross-posting from RPG.Meta.SE; this is a color bug specific to RPG.SE.

So Stack Exchange got new colors, and there’s a Meta.SE Q&A about it, but this issue seems to be specific to our site: questions with watched tags get a color highlight, but the contrast between it and regular questions is quite slight, so those questions don’t actually stand out the way they should:

Image from RPG.SE main page showing several questions, two with watched tags and three without, showing the limited contrast between the two

This hasn’t been mentioned on the Meta.SE Q&A because most sites don’t have this problem: their contrast is greater:

Image from Meta.SE main page showing three questions, one with a watched tag, to show the greater contrast

The cause here is pretty clear, too: all sites use --yellow-100 for this highlight color, but our site uses a different background color for regular questions that is much more yellow-ish (#FFFDF7) and thus much closer to --yellow-100 than the white (#FFFFFF) used on most sites. We need either a custom --yellow-100 (and presumably customizations to the other --yellow-### colors to correspond appropriately), or we need a custom rule that doesn’t use --yellow-100 for these questions.

3
  • The contrast in Stack Overflow dark mode is similarly bad, if not worse.
    – Ryan M
    Oct 25, 2023 at 0:52
  • See also ELU, which also has a beige background.
    – Laurel
    Oct 25, 2023 at 19:58
  • We've made a small update to our yellow-100 color. The contrast ratio should be much closer to what RPG had before with contrast between the custom background color and posts with watched tags. Adding a custom color for watched backgrounds isn't an easy fix so I would suggest asking for an update the RPG site background color on RPG meta.
    – Carrott Staff
    Nov 23, 2023 at 21:02
13

ref 497

In the flagging history, questions and answers which are deleted should be shown with a red background (answers are shown as the question title but in smaller text). For some reason, deleted answers do not have the red background anymore but deleted questions still do.

Both the question and the answer in this screenshot are deleted:

Inconsistent red background on deleted question vs deleted answer

Note: The screenshot uses Stack Overflow Dark Mode but this also applies in light mode.

5
  • Side note: I am not sure if the text in the spam and rude flags are supposed to be black in dark mode so this may be another bug
    – CPlus
    Oct 20, 2023 at 16:55
  • 1
    If you inspect the html you'll see that it uses the bg-red-050 class... which, from initial investigation, does not exist. It seems it might be a typo of bg-red-150.
    – Daedalus
    Oct 23, 2023 at 7:58
  • 1
    @Daedalus Previously they had 050 variables. It looks like they removed those in the latest update to the new colors.
    – TylerH
    Oct 27, 2023 at 19:26
  • @Daedalus They changed the names of all the 050 variables, except --black-050 to include -legacy, so --red-050 is now --red-legacy-050 (black has both --black-legacy-050 and --black-050. All of the associated classes which stood in for a single 050 color assignment also had -legacy added, so there's now a bg-red-legacy-050 class, along with :hover, :focus variants using h\: and f\: prefixes on the class names.
    – Makyen
    Oct 29, 2023 at 19:19
  • 1
    @Carog Thanks! Finally this may be fixed.
    – CPlus
    Nov 27, 2023 at 23:22
11

ref 488

Background too dark on highlighted sections of comment formatting help:

enter image description here

The dark background

.comment-help code {
    background-color: var(--blue-400) !important;
}

is a bit too dark against black text, perhaps lightening it up to:

.comment-help code {
    background-color: var(--blue-300) !important;
}

enter image description here

is in order?

At the very least, this problem present on this site and SO.

1
  • 1
    Ooff that's bad and even worse in HC mode, thanks for reporting. Agree with the suggested change, I've logged to make updates to both default and High Contrast mode to make sure we meet contrast standards.
    – Carrott Staff
    Nov 22, 2023 at 22:51
11

ref 486

Were the green/ red diff highlight colors (e.g. that show up in revisions) touched at all? The green looks darker to my eyes, and the contrast is somewhat poor, but I have no idea whether this was actually adjusted or not:

Revisions page showing red and green highlighting throughout the diff

Both colors are a little difficult to read and roughly on par with each other, with an Lc score of about 60 each (Red: 60.17, Green: 59.71). Given, I do understand that this text isn't designed to be read quite the same way as standard body text, but it caught my eye and seemed worth calling out.

Dark mode colors appear to fare... about the same, if marginally better by the numbers at ~67 (Dark mode red: -65.96, Dark mode green: -67.73):

Another revisions page showing both diff colors, this time in Stack Overflow dark mode

3
  • 3
    " I do understand that this text isn't designed to be read quite the same way as standard body text" I disagree; it very much is meant to be read in the same way as standard body text, at least when reading the revision history. I agree with you that this is hard to read, and could be improved (especially for suggested edit review, assuming it uses the same colors).
    – Ryan M
    Oct 19, 2023 at 23:50
  • 2
    I struggled with cognitive overload when reviewing suggested edits under the previous design: seconding that we shouldn't make it even worse.
    – wizzwizz4
    Oct 20, 2023 at 22:18
  • 1
    Our main struggle with diff highlight colors is getting 3 shades of the same color to work and still be legible — in some cases we have 2 background shades of red and 1 shade for text all on top of each other (that still needs to pass contrast standards). However, in a lot of cases we only need 2 shades like your screenshot (1 background shade and 1 text shade) so I'll see if there's a graceful way to improve our 2 shaded use cases without breaking the 3 shaded cases.
    – Carrott Staff
    Nov 27, 2023 at 23:35
10

The "Share" link stands out from the other buttons under a post when marked as visited:

The "Share" link under a post is noticeably lighter than the other links in high contrast dark mode.

10

Keyboard shortcut highlights are still invisible in high contrast dark mode

Here is a static screenshot of the question list:

List of posts where the second one is supposed to be highlighted via a selection with a keyboad shortcut. All posts look exactly the same.

When pressing J or K to select different posts it looks exactly the same. Thus I cannot bother with capturing a GIF this time.

One of those posts is indeed selected. To help you find which one, here is a hint: it has the CSS style

.keyboard-selected {
  box-shadow: 15px 15px 50px rgba(0, 0, 0, .2) inset;
}

while the normal background colour is rgba(0, 0, 0, 0), so there should be a partially see-through completely black shadow on the completely black background.

2
  • 2
    The eye-strain for the new colors in dark-mode is blinding.... Oct 19, 2023 at 22:25
  • 2
    It is worth noting that high-contrast dark mode is intended to help with accessibility, which keyboard navigation is also supposed to help with...so it's particularly bad for it not to work in this mode.
    – Ryan M
    Oct 20, 2023 at 0:05
10

Something about this rollout seems to have messed up the contrast on the chat.SE topbar. The username and "mod" links are now very difficult to read:

The chat.SE topbar with the "Mithical♦" and "mod" links very difficult to read

I've verified that this is not being caused by any userscripts.

The same thing happens on chat.Meta.SE.

It's entirely impossible to see on chat.SO:

chat.SO with nothing visible where the user link is

The link is still there but it's impossible to see.

1
  • For me it is just username - as I am not a moderator. But I can confirm that it looks the same for me; the username is almost invisible. (I was about to report this problem - I am glad to see that it is already reported.)
    – Martin
    Oct 21, 2023 at 8:33
10

Not a bug, but an annoyance.

I'm sure I'm not the only one here using Dark Reader to cope with SE's archaic lack of a Dark Mode.
Before this update I was able to clearly see whether or not I had voted on a question, but now I can barely tell, except for the slightly brighter outline of the button:

enter image description here

↑ This is an upvote

Trying to figure out why this happens:

A theme-base-primary-color is added to the colour scheme (disabling it reveals that the underlying color palette is likely that for Stack Overflow; disabling --theme-base-primary-color-l turns Meta's color scheme orange [which could also explain why Dark Reader sometimes shows the banners here as orange rather than blue, but I digress]).
The culprits seem to be the orange values (specifically --orange-100 and --orange-500) in body:not(.theme-highcontrast):not(.theme-dark)), but I can't figure out why they aren't changed or even changed by Dark Reader.

This also brings up a second matter: why is the CSS for SE so convoluted? Why are so many overlapping and hierarchized style changes being parsed on every single site? Can't individual domains trigger their own specific code blocks?

4
  • 1
    The CSS is convoluted because the HTML has just been evolving for the past two decades, and is far too convoluted to use CSS selectors on easily, so the styling has to be inline in the HTML. Stacks is rather impressive for what it is (a better, more domain-specific Bootstrap), and they've been chipping away at making individual pages… perhaps not all that much better, but certainly more consistent. Individual sites used to trigger their own specific code blocks, but they found that too hard to maintain.
    – wizzwizz4
    Oct 20, 2023 at 13:58
  • Thanks for raising this. I also use Dark Reader for most SE sites (I use the official dark mode on SO), but I've had to disable Dark Reader because of this vote button issue.
    – Robotnik
    Oct 23, 2023 at 23:16
  • @Robotnik As a workaround, I've set Dark Reader to use "Filter" instead of the "Dynamic" theme generation mode for SE sites. It's uglier but it's easier to see whether I've voted on a question while having dark mode. Oct 24, 2023 at 3:56
  • @galacticninja Oof, yeah, filter mode is pretty ugly, but thanks, at least my eyes aren't burning and I can see if I've voted now :)
    – Robotnik
    Oct 24, 2023 at 4:09
10

ref 459

The contrast between the new moderator tag color scheme and the question-with-watched-tag background highlight is somewhat poor:

Question on the questions page with a watched tag, with the highlighted background that comes with it

9

Stack Exchange Toolbar - Stack Exchange Menu

When editing YOUR COMMUNITIES the ADD button is "invisible"

Stack Exchange dropdown - edit mode

Steps to reproduce

  1. Sign in to a Stack Exchange account.
  2. Go to any Stack Exchange site.
    I check this on:
    • Meta Stack Exchange
    • Webmasters SE
    • Web Applications SE
  3. Click the Stack Exchange Menu > (YOUR COMMUNITIES section) Edit.
    This should display something like the above snapshot.

Environment

  • Mac Mini M1
  • Chrome with several extensions, like Grammarly, TamperMonkey, Diigo and others.
    The extensions that modify the styles of general sites, like Stylebot and TamperMonkey are turned off. I didn't try on Incognito with all the extensions disabled.
2
8

The one I've visited looks unvisited, and the one I haven't visited looks visited. Can you guess which is which?

reverse visited colours

4
8

Horizontal scrollbar in topbar is too hardly visible on dark mode with narrow screen on mobile:

enter image description here

8

The vertical alignment of question score to question title in the Linked/Related sections looks very odd when the text only takes up a single line:

Screenshot of the Linked section showing a title misaligned with the question score

Less of an issue, but in the same area: Question scores with an accepted answer are fractionally taller than questions without (as the green box has a 1px border that the grey box does not):

Comparison of two question score elements

(It's possible this has always been the case, but I could swear they used to line up)

8

Very poor distinction of visited inline links

The colour for visited links is so close to the normal text colour as to be practically indistinguishable

Visited Link
visited link dark mode
visited link light mode

For comparison, here is the same link in the un-visited state

Un-visited Link
unvisited link dark mode
unvisited link light mode
8

ref 459

When I view a deleted post (example), the contrast between the red/pink background and the tags isn't great.

enter image description here

I don't have a specific suggestion in mind, but is there a way to increase the contrast between the red background and the tags (other than something like a userscript)?

2
  • Not great in dark mode either i.stack.imgur.com/Np7zU.png
    – Phil
    Oct 20, 2023 at 2:04
  • 2
    Agree, don't love this. I think we can play around with it.
    – SpencerG StaffMod
    Oct 20, 2023 at 13:44
8

The tag didn't get the new design: (for some it did, based on comments.)

featured tag still with previous design

According to this very announcement, it should be very different:

featured tag as it should look like

11
  • 1
    Maybe I'm stupid, but it does have it, I think. Wasn't it red before?
    – CDR
    Oct 19, 2023 at 18:21
  • @CDR heh let me hard refresh... nope, that's what I see, even after clearing cache. That's on the server side. Maybe the new CDN, i.e. based on location, caching old CSS. Oct 19, 2023 at 18:21
  • @CDR: Yep, it was. It's definitely changed.
    – V2Blast
    Oct 19, 2023 at 18:21
  • In your screenshot, the tag you circled looks like it has the new color, doesn't it? It seems to be orangeish now. Oct 19, 2023 at 18:24
  • @CaveJohnson I honestly can't see any difference from before. It was exactly like that, maybe different tint of red. According to the post, it should be blue, so really don't know what's going on. Oct 19, 2023 at 18:25
  • 1
    The "featured" tag is a mod-only tag (orange), not a required tag (blue). Edit: oh, I see, yeah, something's wrong (either the announcement or the implementation). Oct 19, 2023 at 18:27
  • @MetaAndrewT. that's not what the announcement says, they clearly claim to change it. It's mod-only, but special as it's not related to the status, so always caused trouble. ;) Oct 19, 2023 at 18:30
  • 13
    Featured is a mod tag and should be orange. I took a quick screenshot from internal documents so my screenshot is wrong and the current implementation is correct. I'll fix my post.
    – Piper Staff
    Oct 19, 2023 at 18:38
  • Added the status-completed tag since the screenshot has been corrected has on the post.
    – Carrott Staff
    Nov 22, 2023 at 22:54
  • @Carog thanks, but I wonder about "you may see a reference number added next to the status tag on your post" - this is pretty big change, maybe worth announcing it on its own, not as part of colors update which isn't really related? Nov 23, 2023 at 7:30
  • @ShadowWizardIsSadAndAngry So far I'm only doing it on the 2 color posts. I'm testing out a new process for keeping track of issues that came up from the color change specifically. If it helps and we want to keep doing it in the future on all posts, we'll announce something more general on meta. The team/process for managing issues related to colors is a bit different than the usual so it might just be an edge case.
    – Carrott Staff
    Nov 23, 2023 at 17:13
8

ref 491

In the revision history of a question, the color of the gold badge icon next to a user is too dark and is almost indistinguishable from the color of the bronze badge icon:

enter image description here

Normal-looking colors in the top bar:

enter image description here

8

ref 498

Duplicated border in help center

The navigation menu on the right side of this help center article (and likely others) has a duplicated and offset top border. Can it be removed, as it looks weird?

Actually, this seems to be more general. I also see it on Custom Filters, Watched Tags, Featured on Meta, and "disclaimers" (i.e., on law.SE), so it might be an issue with the boxes more generally.

enter image description here

1
  • I'm seeing something a bit different on my end but there's definitely something weird going on with extra borders. I've logged it with the team to investigate.
    – Carrott Staff
    Nov 27, 2023 at 23:53
7

Oddly jarring colour changes of new posts notification in high contrast dark mode

The colours for normal: Normal new post notification in high contrast dark mode.

hover: Hovered new post notification in high contrast dark mode.

and click: Clicked new post notification in high contrast dark mode.

of the post notifications are rather dissonant and highly distracting. Especially the shift to and from clicked looks very jarring

Animation showing the transition from normal, to hovered, then finally clicked new post notification which leads to an abrupt flash of bright colour when clicking.

7

Well, this is even worse (seen on this revision page:

seemingly padding-less tag

I first thought, it was just the padding-less green-ish stipe but there's actually a border I can hardly see on my screen. I only noticed it due to hovering over it.

hovered state

It's just the diffing, I understand, but this shouldn't be more prominent than the actual tag itself.

1
7

Inconsistent colouring between Stack Snippets editor and code blocks in posts

The Stack Overflow snippets editor uses the bleached colours 🤢 but when the code is displayed in the post, it is back to its glorious, vibrant self 😌.

It's more noticeable in dark mode but inconsistent in both.

Snippets editor

Dark Mode Light Mode
snippets editor dark mode snippets editor light mode

Post

Dark Mode Light Mode
code block dark mode code block light mode
7

When I touch the edit button it turns black. If I edit the post it's natural that the button remains black for me (to show it's edited). But if I don't edit the post and click on the back button, the edit button is still black for me. In this case even if I reload the page the button is still black. Does it remain black to show me I once clicked on the edit button on that post?

edit1

edit2

This occurs on Meta and all other SE sites. I hadn't seen this prior to the recent global changes in sites.

Update: It should be fixed so that only when I actually edit the post the button remains black. Because if it remains black as I once opened the edit page and closed it without editing I will wrongly think that I have edited the post after I encountered it later.

4
  • 2
    Well that's typical for using back button so not sure if considered a bug. Can also reproduce on desktop if middle clicking with a mouse to open edit in new tab, the edit link stays in "active" state. Oct 22, 2023 at 11:45
  • @ShadowWizardIsSadAndAngry I have edited my answer with more sentences.
    – user718628
    Oct 22, 2023 at 13:10
  • Also, you are speaking about letting the edit page to remain opened in a new tab. But I'm speaking about "not editing" and clicking on the back button.
    – user718628
    Oct 22, 2023 at 13:13
  • 2
    Looks like they applied it to the visited state of the link, not sure how it was before. But yeah, once you visit the link once, the color will stay black for good, on the same browser. It doesn't check if you actually edited or not. Oct 22, 2023 at 13:19
7

The Looking for your Teams? button in the left sidebar has the left part of the border chopped off. Could it be updated to have the border go all the way around it?

Screenshot of bug with freehand red circle

3
  • 1
    Oh interesting, I don't see that outer glow / border unless I right-click.
    – Aaron Bertrand Staff
    Oct 19, 2023 at 18:48
  • 2
    (Or single-click, to trigger the dialog, which was... unexpected.)
    – Aaron Bertrand Staff
    Oct 19, 2023 at 18:54
  • Looks like this is fixed now, thanks for reporting. Cause was related to: meta.stackexchange.com/a/393950/888623
    – Carrott Staff
    Nov 21, 2023 at 20:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .