This is not an encoding issue, but it is actually a bug in some versions of Google Chrome, which is unlikely to sound. I think that at the moment there are no corrections, we just need to wait until Google solves their problem, knowing that Google will be made from the moment they are clarified. Let the hope.
source
share