9

Currently, this failed flagging box is colored as informational (blue), not error (yellow), e.g.:

enter image description here

FR: Color the failed flagging box as an error, not as informational.

By contrast, informational boxes are typically in blue:

enter image description here

and error boxes are typically in yellow (at least with my browser config):

enter image description here

Not trying to nitpick but I sometimes use colors to avoid reading.

Note: Chrome's dark mode is on in these screenshots but that doesn't change the fact that the flagging box is using the same color as informational boxes.

Additional screenshot: this failed flagging box is also colored as informational (blue) on SO dark mode:

enter image description here

Improve this question
10
  • Wouldn't this be a bug? I mean, I highly doubt it's intentional. Could be wrong, though. Commented Feb 15 at 23:40
  • @security_paranoid maybe, idk Commented Feb 15 at 23:41
  • 3
    Super User has no official dark theme, so it's not a bug and nothing SE should be doing. The problem is in whatever you're using to have a dark theme. Commented Feb 16 at 8:23
  • 1
    OK then, you are asking Stack Exchange to change its design in order to support non official theme. It's on topic, but I still disagree with this, as I don't think SE should spend their time on supporting external themes, as most likely this will cause other bugs and problems to the official design itself, which in turn they won't fix for years. I don't want that. Commented Feb 16 at 8:46
  • 3
    When reporting design bugs, or asking for change in design, it's crucial to use the site as seen by "default", not with external themes/modes/etc. Commented Feb 16 at 8:50
  • 6
    @ShadowWizard how does that change the question? Commented Feb 16 at 8:55
  • 5
    Indeed, it does not change the question, the bug remains relevant and your report is legit. However I think it is generally more convenient when nothing distracts visitor from the bug itself. Like, if there were unicorns and waffles in your browser viewport due to some userscripts, that would not render your bug report invalid, but would make it less easy to perceive. For example, dark theme distracted Sha from your bug report and he thought that you're reporting a different thing (though your post definitely states what you're reporting, but I think it's clear what I'm talking of) Commented Feb 16 at 11:45
  • 2
    @nicael it's indeed distracting, and when I see screenshot showing something that I don't see, I just assume that something else is at play, something for which Stack Exchange is not responsible. And indeed, SE can't be expected to "support" Chrome's dark theme. If the same issue exists in standard Chrome, seen without any themes, then I'd like to see that in a bug report or feature request, hence the seen by "default" which I said before. So while the feature request here is valid (I retracted the close vote) it's still poorly given, for me. Commented Feb 16 at 12:00
  • 2
    @ShadowWizard Feel free to add images. It's more constructive than downvoting a valid FR/bug report. Commented Feb 17 at 0:47
  • 2
    The custom dark mode does make it harder to find the route of the problem, in this case it looks fairly straightforward. I agree, this flagging dialog box should be using s-notice__warning class to make it yellow. I've logged it as a bug for the team to dig into. It's likely a quick fix but fairly low priority since it's not preventing anything. Commented Feb 19 at 19:00

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.