You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 29, 2023. It is now read-only.
A video's comments lack the vote arrows after about five seconds of the video (this may just be how long it takes for everything to "set up," in my limited vocabulary), and after a bit of scrolling I found the comments' arrows, both upvote and downvote, arranged in a row to the left of a random comment. The arrows beneath this particular comment were not affected. The arrows can be used to vote on their corresponding comment. Both parent and child comments are affected. Minimizing the comment affected only properly hides the comment and its set of arrows; the stray arrows tag along to the next comment instead.
I've included some screenshots. After the taking of these screenshots, I tried reloading the page, which resulted in the arrows reverting to their position on the page before the reload. It is possible to lower the arrows down the page with every reload. As the arrows descend with each reload, any comments they "pass" gives up its arrows to the collection.
Ignore the seemingly random shelf positioning.
25 vote arrow sets tagged along with the usual set in this instance. There are two unaccounted-for sets.
Voting with the stray arrows properly altered the score of the corresponding comment.
Minimizing all comments left the arrows hanging in a gray space. The arrows were not to be found when all comments had been minimized.
Resulting gray space, appearing both above and below the bottom YouTube bar. The gray field continues on below this bar. The arrows are still nowhere to be found anywhere on the page.
Opening (un-minimizing?) the comments showed the stray arrows again. The arrows return to the usual comment if all comments are reopened. This screenshot shows the still functional stray arrows hanging around the bottom bar.
All still-functional arrows lowered by reloading. Every comment has been stripped of its arrows.
The text was updated successfully, but these errors were encountered:
A video's comments lack the vote arrows after about five seconds of the video (this may just be how long it takes for everything to "set up," in my limited vocabulary), and after a bit of scrolling I found the comments' arrows, both upvote and downvote, arranged in a row to the left of a random comment. The arrows beneath this particular comment were not affected. The arrows can be used to vote on their corresponding comment. Both parent and child comments are affected. Minimizing the comment affected only properly hides the comment and its set of arrows; the stray arrows tag along to the next comment instead.
I've included some screenshots. After the taking of these screenshots, I tried reloading the page, which resulted in the arrows reverting to their position on the page before the reload. It is possible to lower the arrows down the page with every reload. As the arrows descend with each reload, any comments they "pass" gives up its arrows to the collection.
Ignore the seemingly random shelf positioning.
25 vote arrow sets tagged along with the usual set in this instance. There are two unaccounted-for sets.
Voting with the stray arrows properly altered the score of the corresponding comment.
Minimizing all comments left the arrows hanging in a gray space. The arrows were not to be found when all comments had been minimized.
Resulting gray space, appearing both above and below the bottom YouTube bar. The gray field continues on below this bar. The arrows are still nowhere to be found anywhere on the page.
Opening (un-minimizing?) the comments showed the stray arrows again. The arrows return to the usual comment if all comments are reopened. This screenshot shows the still functional stray arrows hanging around the bottom bar.
All still-functional arrows lowered by reloading. Every comment has been stripped of its arrows.
The text was updated successfully, but these errors were encountered: