Timeline for Color the failed flagging box as an error, not as informational
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19 at 19:00 | comment | added | Carrott Staff | 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. | |
| Feb 19 at 18:57 | history | edited | CarrottStaff | edited tags; edited tags | |
| Feb 17 at 0:47 | comment | added | Franck Dernoncourt | @ShadowWizard Feel free to add images. It's more constructive than downvoting a valid FR/bug report. | |
| Feb 17 at 0:47 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 | added 204 characters in body |
| Feb 16 at 12:02 | review | Suggested edits | |||
| Feb 16 at 12:53 | |||||
| Feb 16 at 12:00 | comment | added | user152859 | @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. | |
| Feb 16 at 11:45 | comment | added | nicael -misses Sha- | 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) | |
| Feb 16 at 8:55 | comment | added | Franck Dernoncourt | @ShadowWizard how does that change the question? | |
| Feb 16 at 8:50 | comment | added | user152859 | 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. | |
| Feb 16 at 8:46 | comment | added | user152859 | 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. | |
| Feb 16 at 8:43 | review | Close votes | |||
| Feb 16 at 8:50 | |||||
| Feb 16 at 8:42 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 | stating the obvious to address a comment |
| Feb 16 at 8:23 | comment | added | user152859 | 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. | |
| Feb 15 at 23:41 | comment | added | Franck Dernoncourt | @security_paranoid maybe, idk | |
| Feb 15 at 23:40 | comment | added | security_paranoid | Wouldn't this be a bug? I mean, I highly doubt it's intentional. Could be wrong, though. | |
| Feb 15 at 23:33 | history | edited | Franck Dernoncourt | CC BY-SA 4.0 | deleted 6 characters in body |
| Feb 15 at 22:59 | history | asked | Franck Dernoncourt | CC BY-SA 4.0 |