Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Start a new query. Put in something that is correct syntax. E.g.


Click Run Query and the correct results are displayed.

Make it a syntax error. E.g.


Click Run Query and the correct error is displayed (and the previous results are not cleared).

Click Run Query again and the error is cleared* (but the previous results remain).

Click Run Query again and the error is displayed again.

Correct the query so that it should display new results. E.g.


Click Run Query and the previous error is cleared and the new results are displayed.

*The error cleared should be replaced by the new error. (Note you can change the query so that it should display a new error, e.g.


and if there was an error displayed from the last query, this query will still just clear the error and leave the previous results.)

share|improve this question
He's talking about the use of the SE Data Explorer, so this isn't a wayward SO question. – jonsca Jan 17 '12 at 10:53
up vote 4 down vote accepted

The problem is that Data Explorer is so incredibly responsive that your error was reported back to the browser before the fade out animation on the error box finished.

This left the error box in an incorrect state in cases where the error box was visible when you submitted something that would then subsequently return an error. If the animations are annoying, they can just be removed, but for right now I created a fix by making sure the animations are stopped irrespective of state before the new response is processed.

...Of course, that can lead to a situation where the error box remains when it shouldn't, which I've now also addressed.

share|improve this answer
I'll wait for this to go live before accepting it. – Mark Hurd Jan 18 '12 at 0:46
I've unaccepted this for the moment because the problem is effectively back again, at least in Chrome. – Mark Hurd Apr 2 '12 at 5:37
The form is a little different, but it is, yes. Fixed already, but not deployed until I finish up some other stuff and get a chance to talk to waffles. – Tim Stone Apr 2 '12 at 5:38
Yes, I saw it was probably fixed, but I thought I better flag it just in case :-) – Mark Hurd Apr 2 '12 at 5:40

You must log in to answer this question.

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