What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 150 Stack Exchange communities.

Even if I dismiss a badge notification ("You have earned the ... badge for question ...") using the close button at the right of the message it gets redisplayed again and again when I refresh the page until I open a new session.

Working with Safari 5.0.3 (6533.19.4) on Mac OS X 10.6.5.


I just created a new account at writers.se, and all three messages (Welcome, associated with, earned rights) kept appearing even after having gone to meta and back. Only jumping into a question and coming back to the main page made them go away. (Click them away using the close button for each, go into a question, and come back to the main page.)

share|improve this question

migrated from meta.apple.stackexchange.com Dec 28 '10 at 9:15

This question came from our discussion, support, and feature requests site for power users of Apple hardware and software.

Does it happen on other SE sites, or just on Apple? –  Kyle Cronin Dec 27 '10 at 17:34
@kyle - Haven't gotten a badge on another site lately. I will let you know as soon as possible. –  malach Dec 28 '10 at 5:48
@kyle - it happens in other sites as well (maybe only beta sites). –  malach Dec 28 '10 at 8:20
@Ralph OK, since it's happening on multiple sites it's probably best to file a bug report on meta.stackoverflow.com. If you want, I can migrate this question there directly. –  Kyle Cronin Dec 28 '10 at 8:50
@Kyle - please do so. Thanks. –  malach Dec 28 '10 at 9:06

1 Answer 1

up vote 1 down vote accepted

We can't reproduce this -- have you tried clearing your browser cache?

Also note that clicking "back" will take you back to the previous state of the page, regardless of whether you have clicked the X to dismiss notifications.

share|improve this answer
I did not click "back" but refreshed the page by clicking on the title of the page. It happens reproducibly even after clearing the browser cache. –  malach Dec 28 '10 at 9:08
@Ralph your browser is incorrectly returning the cached page, there is no other way for this to happen –  Jeff Atwood Dec 28 '10 at 13:04

You must log in to answer this question.