I'm trying to delete a now irrelevant comment of mine on this question, but I can't. The system hasn't blocked me from deleting comments for a day for deleting too many, so I think that the page is being buggy. I also can't interact with the comment flags, upvotes, or the "bookmarking" star either. What is wrong with the question page?
- 2SE mods, as a chess mod I also can't delete (or edit) the comment.Brian Towers– Brian Towers Mod2020-03-13 19:06:05 +00:00Commented Mar 13, 2020 at 19:06
- 1Indeed. Which is why I have added the status-review tag to bring it to the attention of the level of mods above me.Brian Towers– Brian Towers Mod2020-03-14 18:59:31 +00:00Commented Mar 14, 2020 at 18:59
- I don't see any comments from you on the question itself. Can you clarify which one you want to remove, please? And also, what's happening when you try to delete it? Is the delete link not showing up, or do you get an error?Adam Lear– Adam Lear StaffMod2020-03-18 22:24:03 +00:00Commented Mar 18, 2020 at 22:24
- FWIW, I just flagged the comment for mod deletion by referring to this meta post. See whether the mod tool is possible to delete instead of trying to delete the comment from the post directly...Andrew T.– Andrew T.2020-05-06 14:07:12 +00:00Commented May 6, 2020 at 14:07
- However, it seems really weird since you also mentioned comment flags, upvotes, and favorite (starring)... because I could flag the comment and also favorite the question just now. There doesn't seem any maintenances (read-only status) on that day either...Andrew T.– Andrew T.2020-05-06 14:14:25 +00:00Commented May 6, 2020 at 14:14
Add a comment |
1 Answer
This issue has been fixed.
The root cause was an answer (which happened to be deleted, though the same thing could have happened on an undeleted answer) where the following was included [StartPly "124"], which indicated a starting move on the 62nd move. The only problem is that there were no moves given, and this caused the chess.js script to crash. And due to the way that the script was initialized, it caused execution of other front-side initialization to not be processed, leading to click events not being attached to buttons, etc.
To fix this:
- The actual bug in the chess.js script has been fixed to check for nulls on the proper line to avoid this from happening.
- The way in which the chess.js script is called has been modified to ensure that issues on the script do not affect page init logic.