After I voted for the node, though, the encoding issue was gone
Perhaps not attach too much to it going away after voting. I have an internal webpage that has a similar encoding issue that I cannot debug* because every time I refresh the page, the issue goes away. So any changes I make, I don't know if they have solved the problem or Chrome has decided to display it more legibly.
* of course I could debug it but it is only me and one other person who looks at the page. The encoding bug doesn't affect the information so it is very low priority and just gets looked at occasionally when I notice it.