68Views6Replies

Author Options:

"Repeating Image" comments bug and a workaround Answered

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.

Comments

The forums are retiring in 2021 and are now closed for new topics and comments.
0
rachel
rachel

12 years ago

I have fixed this, and it will be pushed live in the next release. This should be early in 2009 (b/c of the upcoming holidays). An alternate workaround is to refresh the page, or go to the URL bar and hit return; this clears the state as well.

0
kelseymh
kelseymh

Reply 12 years ago

Cool! Thank you so much, Rachel :-) It's good to know that a simple refresh/reload is sufficient.

0
Goodhart
Goodhart

12 years ago

sounds to me like a parameter or pointer is not being reset. Possibly because the "post" instance doesn't reset that one.

0
rachel
rachel

12 years ago

kelseymh, thanks for describing the problem case so clearly. I will investigate it and fix. (It's not a cookie, though; it is javascript, but I think your analysis of leftover state is accurate.)

0
kelseymh
kelseymh

Reply 12 years ago

Ah, okay; you're welcome! I probably shouldn't have made guesses about the internals.

Is this the same code that supports the really cute feature I commented about a while back? Where the contents of a pending reply follows you from one comment to another?