This is retracted but given the context I’m not sure whether it’s still a valid bug report that I don’t understand. Is there a bug report I should action here? If so, can you make it easier for me to understand?
This is retracted but given the context I’m not sure whether it’s still a valid bug report that I don’t understand. Is there a bug report I should action here? If so, can you make it easier for me to understand?
Not a high priority report. Just minor bug. That is, the javascript on the retract button still acts as if it is a delete button. (At least sometimes.) So it looks gone until you refresh. Let me confirm.
Yes. I retracted the parent and it disappeared. I refreshed and it was there again with the strikethrough.
Again, low priority. It could be work to fix (unless, say, you could copy and paste some of the AJAX from the post comment code that loads the new comment code from the server when it is submitted.)
I wish the server was as smart as the AJAX. The AJAX on the ‘retract’ button still knows how to make removed stuff invisible!
This is retracted but given the context I’m not sure whether it’s still a valid bug report that I don’t understand. Is there a bug report I should action here? If so, can you make it easier for me to understand?
Not a high priority report. Just minor bug. That is, the javascript on the retract button still acts as if it is a delete button. (At least sometimes.) So it looks gone until you refresh. Let me confirm.
Testing again.
Yes. I retracted the parent and it disappeared. I refreshed and it was there again with the strikethrough.
Again, low priority. It could be work to fix (unless, say, you could copy and paste some of the AJAX from the post comment code that loads the new comment code from the server when it is submitted.)