Threaded Comments Makey Breaky
![]() ![]() |
Thanks bunches for this anti-Thor tool, SBP. Unfortunately, the comment threading on POWIP kind of breaks the script. Good example: try hammering any of his new sockpuppets on the NEA thread. Watch what happens, for instance, when you try to make "fugue" go away. Make sure to scroll down past the hammered comment. UPDATE: Of course, the new site update totally trashes the Hammer. However, I did find a way to get it to deal more properly with threaded stuff before the change, and have updated it to match the new internal tagging. Here's the relevant code fragment near the top of the main for loop:
comment = document.getElementById(comments[i]);
var commenthash = extractIdentifier(comment);
var commentbody = document.getElementById("div-comment-"+commenthash);
if (commentbody == null)
commentbody = comment;
var trollname = extractUserName(comment);
(In the previous POWIP the internal ID to look for was "comment-body-(number)" instead of "div-comment-(number)".) What this does is isolate the actual part of the comment block that has the comment text, instead of the whole comment block, which contains both the text and the reply-comments. All page changes that happen within the loop should thus be applied to commentbody, not comment. |

