Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

HTML page content type has charset=iso-8859-1 but document.characterSet is 'UTF-8'

  • 2 antwurd
  • 2 hawwe dit probleem
  • 5 werjeftes
  • Lêste antwurd fan gilles.poirot

more options

Hi,

I'm a web developer and I have an issue document.characterSet property from DOM API has an incorrect value on a non UTF-8 page

Firefox version: 95.0.2

1. HTML page is returned with following content-type content-type: text/html; charset=iso-8859-1

2. JavaScript code in the page reads document.characterSet property

Expected characterSet value is "ISO-8859-1"

Actual characterSet value is "UTF-8"

Thanks and regards,

Hi, I'm a web developer and I have an issue document.characterSet property from DOM API has an incorrect value on a non UTF-8 page Firefox version: 95.0.2 1. HTML page is returned with following content-type content-type: text/html; charset=iso-8859-1 2. JavaScript code in the page reads document.characterSet property Expected characterSet value is "ISO-8859-1" Actual characterSet value is "UTF-8" Thanks and regards,

Alle antwurden (2)

more options

What encoding does the server send ?

If the server sends encoding "UTF-8" then that prevails and Firefox ignores a possible specification in the actual file for security reasons.

more options

I observed this behavior while working on a customer incident. The server responds with a content-type header which is "text/html; charset=iso-8859-1"

I tried to reproduce on a sample but in my test, I get the expected "window-1252".

However, if the response body contains an UTF-8 BOM, content-type header is ignored and document characterSet is "UTF-8"

Here is a small sample https://glitch.com/edit/#!/document-charset

Is this the intended behavior?