Frans wrote on Feb 5, 2021, 14:50:
But I don't know the reason nor remedy for this yet; it's really weird that the browser only renders UTF-8 characters correctly and consistently if they're 3-byte ones (and then the 2-byte ones too), but not if a page includes only 2-byte characters, given that HTML and HTTPS instruct it to use that character set.
Yes, a workaround remedy may be to insure that the page always includes a 3-byte character somewhere, but I'd still like to understand the underlying problem if possible.
I was going to add one more weird observation about the replacement characters, but since last night I'm not getting them anymore during dozens of refreshes in multiple browsers. So perhaps the issue resolved itself just as mysteriously as it popped up...