Ignoring the last 2 lines from this anon poster, I think it's indeed funny for them to just using a mere inspect element on this.
Since actually it didn't work like that.
While it's true that there maybe some shady things going on, since IU also got this kind of thing, I feel that dive is kinda... misleading with their methods. Because it's actually more on their server's data, rather than the displayed page (the HTML)
okay let me explain:
1. This popup thingy showing the charts
it's not that as simple as that twitter dive pointed out.
The way they display the number is by requesting the numbers to the server and displaying it back on that page.
It's not manually coded because it would be reaaallyy tiring to typed or even just copy-paste all of that number 
So they are like, using a template to show the structure, and they can just call the data needed on each row.
Using a sniffing tools, we can actually get what kind of data that are queried by that site.
You could see the queried result in this link
and it will show this
It's more of "rigged" on the server-side rather than the client-side (in browser/HTML); like that dive claimed.
because if you check out that link I gave above, the 6th data (the one with hangeul) is saying:pasted-from-clipboard.png
hence that's why when the data is displayed, it will say "repair" or something like that. (YT is the 6th row)
2. The acclaimed inspect element
so why that dive draw a conclusion by using an inspect element?
The brief explanation is like this:
So all that data displayed is in a form of list.
and the method used by that dive is deleting the list element holding/containg the "repair" data.
and since they delete the list not the data it self, the code will simply just making the next list element to fill the order.
but notice that the Bugs' Song chart realtime? yes the number is gone because the list had been pushed up.
That's why the youtube number could automatically filled with #1 when deleting the "repair" element, because the list's order got change by deletion.
(imagine like when you queued up to buy an ice cream and you are on the middle. If somehow, someone in front of you decides to leave the queue, then you will be automatically filled their queued order right? Because you are the next in line).
3. The conclusion
Just like I said above, while there may be a shady things going on (and it's not just for IVE but also happened to other artist as well), that shady things is not happening in the client-side (in the browser/html) and more likely in the server side, since the queried data is also showing "repair" for YT's place (6th order).
So their method is misleading, because deleting the html element will simply change the data order, making the YT number filled with FLO's number and so on so forth.
anyway update:
It may be not a shady thing at all, considering it's Chuseok day
update 2 :
Finally Instiz correct it
