I earlier asked Dismissing messages, on which Anna Lear answered and I commented on that answer. I assume that I don't get a reply because is included, that's why I ask this new question.

Anna Lear:

These notification messages should now disappear on their own without any clicking required at all.

However, here is a list of messages that still have crosses to close them:

  • You can accept this answer in x minutes
  • You can't vote for your own post
  • Thanks, we'll take a look at it (after flagging)

Can this be fixed? As Olin Lathrop points out this is very annoying behaviour.

  • \$\begingroup\$ You probably did not get a response because she gets ~100s of inbox notifications when she logs in. Probably accidental oversight. \$\endgroup\$ – Kortuk Feb 19 '13 at 14:39
  • \$\begingroup\$ Yes, and I respect that! It wasn't meant as a reproach, sorry for that. \$\endgroup\$ – user17592 Feb 19 '13 at 14:48
  • \$\begingroup\$ I did not think you meant it that way, just explaining, pinging community managers is not always the best way to get a response as they likely get hundreds. We ping them randomly in the TL just to keep them on their toes. \$\endgroup\$ – Kortuk Feb 19 '13 at 14:59
  • \$\begingroup\$ Okay. What happens to this question now? Is someone working on it? \$\endgroup\$ – user17592 Feb 20 '13 at 15:15
  • 1
    \$\begingroup\$ They can track tags cross site, so they will see this bug and respond. Plausibly they will just update it when they fix it / tell you if they wont or tell you status planned if the result is a ways off. \$\endgroup\$ – Kortuk Feb 20 '13 at 15:28
  • \$\begingroup\$ Oops, sorry. I'll pass this on. :) \$\endgroup\$ – Adam Lear Feb 20 '13 at 19:50
  • 1
    \$\begingroup\$ These are all definitely on the list to fix. \$\endgroup\$ – Jeremy T Feb 22 '13 at 16:27
  • \$\begingroup\$ @JeremyTunnell I see things have changed. The messages I've seen up to now disappear on their own, thanks! I see some irregularities though. Are you done already or am I just too quick with shouting again? ;-) \$\endgroup\$ – user17592 Feb 24 '13 at 8:35
  • \$\begingroup\$ You may want to give us a couple of more days, but fixes went out today for a lot of them. \$\endgroup\$ – Jeremy T Feb 25 '13 at 15:10
  • \$\begingroup\$ Sorry, I should also add that we decided to leave the crosses, but make errors click to close. \$\endgroup\$ – Jeremy T Feb 25 '13 at 16:01
  • \$\begingroup\$ @JeremyTunnell thanks for all the improvements! One question: some messages are blue, others are red. What's the system behind that? \$\endgroup\$ – user17592 Feb 28 '13 at 14:18
  • \$\begingroup\$ Basically we are reserving red for errors only. There are places where we couldn't differentiate for technical reasons - and places we're still working on - but looking forward, red should always mean error \$\endgroup\$ – Jeremy T Feb 28 '13 at 16:43
  • \$\begingroup\$ @JeremyTunnell that's clear. Thanks a lot! \$\endgroup\$ – user17592 Feb 28 '13 at 17:20
  • \$\begingroup\$ @JeremyTunnell sorry to bother you again, but the "Thanks, we'll take a look at it"-message after flagging a post is red. Is that meant this way? Because I wouldn't see it as an error. \$\endgroup\$ – user17592 Mar 4 '13 at 15:47
  • \$\begingroup\$ We've still got a few stray ones. It's on the list, thanks. \$\endgroup\$ – Jeremy T Mar 4 '13 at 16:57

As Jeremy said in the comments, these error messages still have Xs to dismiss; but they also can be closed by clicking them (as before), and now fade away after a set period of time.

Think some of the colors may still be being tweaked though.


You must log in to answer this question.