The grace period notice for bounties is like this (for example):

This question had a bounty worth +50 reputation from gparyani that ended 23 hours ago.You have 10 minutes to award the bounty

The current answer(s) are out-of-date and require revision given recent changes.


If you look at the Markdown or press F7, you can see that there is no space between "ago." and "You". When will this typo be corrected?

  • 6
    And here I thought it was just bad keming. – BoltClock's a Unicorn Oct 30 '13 at 17:22
  • @BoltClock'saUnicorn I thought so too, until I pressed F7 and discovered this bug. – user215114 Oct 30 '13 at 17:39
  • 1
    @BoltClock'saUnicorn I think you mistyped. You typed "m" instead of "rn" in "kerning". F7 told me that too... – user215114 Oct 30 '13 at 17:41
  • @gparyani He's mocking the bad kerning that makes rn look like m. – michaelb958--GoFundMonica Oct 30 '13 at 20:50
  • There was no bug; you had an invisible character in your markdown (don't know why...) anyway, edited. @Bolt lol, you tricked me there :D I didn't even notice until I read the comrnents :P – Doorknob Oct 30 '13 at 22:38
  • @Doorknob The F7 key is very useful, isn't it? I didn't find it until I looked at the revision history and scrolled through it using the caret cursor... – user215114 Oct 31 '13 at 4:49
  • @gparyani F7? Don't you mean F12? – Doorknob Oct 31 '13 at 12:56
  • @Doorknob F7 enables Caret Browsing in Internet Explorer, which puts a movable cursor through the page as though it is a document. I can then use the arrow keys to find invisible characters as well as this problem. – user215114 Oct 31 '13 at 14:57
  • @Downvoter Could you explain your rationale? – user215114 Oct 31 '13 at 14:59
  • @Doorknob You mistyped too...you inputted comrnents... – user215114 Oct 31 '13 at 15:01
  • Also visible to other users: i.stack.imgur.com/pvp6c.png (Was going to report this myself, but found this existing report.) – Ilmari Karonen Nov 1 '13 at 17:18
  • Should it be one space or two? xkcd.com/1285 – Andy Nov 1 '13 at 18:05

This has been fixed and will be out in the next build.


You must log in to answer this question.