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
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
The result of this is that for non-ASCII characters this produces funky results, such as in the license of one of my extensions. Having that said, I understand my name has funny weird characters, but they aren't as funny and weird as to be ÃÄ�.
Firefox:
Chrome:
Safari:
They all guess, and they all guess wrong 😆.
The text was updated successfully, but these errors were encountered:
On files hosted on Azure Blob Storage (https://openvsxorg.blob.core.windows.net), the content encoding isn't set. The Firefox DevTools explain it pretty well:
The result of this is that for non-ASCII characters this produces funky results, such as in the license of one of my extensions. Having that said, I understand my name has funny weird characters, but they aren't as funny and weird as to be
ÃÄ�
.Firefox:
Chrome:
Safari:
They all guess, and they all guess wrong 😆.
The text was updated successfully, but these errors were encountered: