Several regular users, including myself, have noticed an annoying bug in replying to comments. The two comments before were copied from the same Forum topic, and were made about 1 minute apart. As you see, the second comment has the same image attached as the first, even though gmjhowe did not select add image the second time.This bug is easily reproducible. Reply to a comment in either a forum topic or an I'ble, and attach an image. Now scroll around and reply to a different comment on the same page. You'll see your image appear when you post the second reply. The error, I believe, is that the cookie(s) created by I'bles to save the sate of the first reply is not completely erased when the user completes the posting. The information about attached images is preserved, and leaks through to a second comment on the same page.The workaround I have found turns out to be really simple. Leave the page (for example, by using the Back feature of your browser), and return to the same page by following a hyperlink. Don't just use the browser's Forward feature; that will preserve state and the bug will occur. By following the link to the page "fresh," I'bles will erase the previous cookie completely, and create a new one in anticipation of what you might do on the "new" page.It would be good if Rachel or somebody could fix the cookie-handling bug so this doesn't continue to happen. It's a real pain if you've just written a long second comment, possible with formatting, and then find unexpected images attached to it.