The work around suggested in the answer here appears to be working for me (Thanks @Seth !).

The line you want to change in the original script (autoreviewcomments.user.js) is as follows:

$('#' + divid).find('.comment-help-link').parent().append(newspan);

From the answer provided:

The workaround for this is to change line 683 to:

setTimeout(function() {
    $('#' + divid).find('.comment-help-link').parent().append(newspan);
}, 10);

Personally, I would keep this as only a temporary fix, and monitor the question for status updates.

The work around suggested in the answer here appears to be working for me (Thanks @Seth !).

The line you want to change in the original script (autoreviewcomments.user.js) is as follows:

$('#' + divid).find('.comment-help-link').parent().append(newspan);

From the answer provided:

The workaround for this is to change line 683 to:

setTimeout(function() {
    $('#' + divid).find('.comment-help-link').parent().append(newspan);
}, 10);

Personally, I would keep this as only a temporary fix, and monitor the question for status updates.

The work around suggested in the answer here appears to be working for me.

The line you want to change in the original script (autoreviewcomments.user.js) is as follows:

$('#' + divid).find('.comment-help-link').parent().append(newspan);

From the answer provided:

The workaround for this is to change line 683 to:

setTimeout(function() {
    $('#' + divid).find('.comment-help-link').parent().append(newspan);
}, 10);

Personally, I would keep this as only a temporary fix, and monitor the question for status updates.

The work around suggested in the answer here appears to be working for me (Thanks @Seth !).

The line you want to change in the original script (autoreviewcomments.user.js) is as follows:

$('#' + divid).find('.comment-help-link').parent().append(newspan);

From the answer provided:

The workaround for this is to change line 683 to:

setTimeout(function() {
    $('#' + divid).find('.comment-help-link').parent().append(newspan);
}, 10);

Personally, I would keep this as only a temporary fix, and monitor the question for status updates.