Bugzilla

I looked into this a bit more. internal.1c4100ed6327a97c53fc.js is intended to be UTF-8 and has regular expressions that contain a curly quotation mark as the last character of a regular expression character class, which is denoted with square brackets, like this: ”]

The curly quote is E2 80 9D in UTF-8. The closing square bracket is 5D. 9D 5D is a Big5 byte pair for 㷷 (see https://encoding.spec.whatwg.org/big5.html), so the square bracket gets eaten, which makes the regular expression not compile.

The suggests that the regular expressions aren't working in Chrome, either, but at least they compile in Chrome, since the character class ends up being syntactically valid garbage.

Ikea could fix stuff in Firefox, Safari, and Chrome by using the HTTP header `Content-Type: text/html; charset=utf-8` on the HTML resource (currently missing the `; charset=utf-8` part).

I looked into this a bit more. internal.1c4100ed6327a97c53fc.js is intended to be UTF-8 and has regular expressions that contain a curly quotation mark as the last character of a regular expression character class, which is denoted with square brackets, like this: ”]

The curly quote is E2 80 9D in UTF-8. The closing square bracket is 5D. 9D 5D is a Big5 byte pair for 㷷 (see https://encoding.spec.whatwg.org/big5.html), so the square bracket gets eaten, which makes the regular expression not compile.

This suggests that the regular expressions aren't working in Chrome, either, but at least they compile in Chrome, since the character class ends up being syntactically valid garbage.

Ikea could fix stuff in Firefox, Safari, and Chrome by using the HTTP header `Content-Type: text/html; charset=utf-8` on the HTML resource (currently missing the `; charset=utf-8` part).