2

I have seen an answer to a question on Stack Overflow.

Question - normal

It contains a typo, so it is edited.

Question - editing

The editing shows that it should be fixed, but it isn't.

Link to answer: sticky div in sidebar

I cleared my cache, cookies etc. and then reloaded the page, same thing

EDIT: I went to my friend's house and it wasn't visible on her computer either

Thank you.

Improve this question
6
  • So you still see # in front of the selectors in the actual answer view? But on the revisions page, it shows the fixed version? Also, note that you clear your cache, etc, etc, because people are bound to tell you to do that.
    – Someone
    Commented Feb 23, 2012 at 18:51
  • 1
    The typo being #sidebar -> .sidebar? I see it fixed now with no edit history. I'd guess the original user fixed it at the same time as you, the edit controller registered your submit as a no-change edit and so left your view as the pre-edit version?
    – Rup
    Commented Feb 23, 2012 at 18:53
  • 2
    No idea what you're talking about. Everything looks fine to me.
    – Cody Gray
    Commented Feb 23, 2012 at 18:58
  • Why the downvote?
    – Anish Gupta
    Commented Feb 23, 2012 at 19:51
  • @user986276 Seems like a good question to me... there are tons of legitimate questions like this that get downvoted so don't feel bad about it... my experience has been that people here on meta tend to be extremely trigger happy with the downvotes.
    – Brandon Moore
    Commented Feb 23, 2012 at 23:41
  • Downvotes mean something different here on Meta. This is described in the FAQ. (cc @Brandon) For example, I downvoted because I can't repro the bug. The tag has since been removed, but I still don't think it makes much sense as a support question.
    – Cody Gray
    Commented Feb 24, 2012 at 4:12

3 Answers 3

Reset to default
5

Well, it was my ISP doing some aggressive caching.

I switched to another ISP and now it edits the way it should.

Improve this answer
4

Chain of events:

  • You loaded the page.
  • You saw that the edit had # instead of ..
  • Sometime before you clicked edit, Purmou used his 5-minute grace period to fix the answer.
  • You clicked the edit button.
  • The system loaded the now-present version of the post, which uses the . instead.

Simply reloading the page should bring up what it actually is. Users are always granted a 5-minute grace period in which they can freely edit their post without it being marked as a separate edit.

Improve this answer
1
  • Sorry I failed to mention that I had cleared the cache, cookies, blah, blah then reloaded the page. Editing now.
    – Anish Gupta
    Commented Feb 23, 2012 at 18:55
1

When a user makes a post, they have a 5 minute window in which they can make edits without them being listed explicitly - they will all appear as one final (possibly awesome) post.

What possibly happened is that you made your edit during this window and the OP caught it himself before the window closed.

You can see this post out of the faq index for a complete breakdown of how the editing system works :

How does editing work?

Improve this answer

You must log in to answer this question.

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