Interesting bug in FORUM

i tried to  quote  on a comment which had a chess game in it...and when my quoted comment was posted.. its does not have the game in the quote but a "loading...." icon going forever... i think its a JS bug (same id or something :) ...

here is the thread to the comment...:

http://www.chess.com/forum/view/fun-with-chess/5000-signs-you-dont-know-enough-about-chess?page=46   ( my comment towards the end... in red)

you can try if the same happens with you... then we can confirm this is a bug...

i am using firefox

Quoting you with Firefox

seems ok

friend seems you did not get what i was trying to say.... try to quote this one....  it has a chess game board in it...(just for testing)

self test ...

here goes...

now I see what you mean. I had seen this before, but I really didn't think much about it

i just reproduced it... seems like a bug to me.... plz confirm if others can reproduce the same...

:) looks like we did a better job than the chess.com testing team... :)

Well,  don't waste space and bandwidth with nonessential, nonproductive quoting and the problem will simply dissipate.

I was part of the chess.com testing team :)

:)

You are right.. but a bug is a bug. and there will be genuine scenarios when somebody would want to quote a game.

One instance of a game isn't enough?

quoting a game does not work really. Or should it ?

sure one instance is enough, but the put problem comes from using thequote button. Maybe by default the quote button should exclude games and pictures. The big is annoying

whenever I quote someone's comment and it got a game in it, I usually have it remove and if I want the game there, I'll post it there myself using the pgn.

Simple solution. The problem isn't the quote feature but the abuse of the quote feature through laziness. With judicial usage there would be no issue.

Ridiculous, it is a bug with the quote feature.  Not a very major one though.

The QUOTE button also doesn't work with images, tables or emoticons (see tally-forum-annoyances-ii) .

I agree to all of the above. It is not a major bug. hence the title "interesting bug ..." not "annoying bug..."  but non the less lets call it a bug and leave it there.. calling it a feature :) will be little far fetched..

[purely from a technical perspective] the way its behaving right now is not what the developer intended it to be. and right there it becomes a bug. :)