Popup pages lack Character-Encoding header [FIXED]

[Elberet]

When a page is opened with the nonav=1 attribute set, there will be neither a Meta line nor a HTTP header controller character encoding. As a result, browsers might, depending on configuration and recently used encodings, autoselect UTF-7 to decode the page, which severely breaks up JavaScripts (since, e.g. "+w+" turns into a Unicode character).

[exp]

is there any browser around which will do this @ fall back to an encoding which f00bars javascript?

BYe!
EXP

[wahaha]

[A missing "+" in JavaScript-line]
When you tell Mozilla manually to use UTF-7, it will keep that stored and autodetect pages that don't specify a character set as using that encoding type with a very high likelihood. That's what happened here. The + is a UTF-7 excape char, "+ " was decoded into " ". D'oh.

[Elberet]

Exactly.

However, it rarely happens and is clearly a misbehavior of the client. So I guess it's not necessary to fix it here (unless you want a bonus geek-point).

[wahaha]

My IE just fell for it... the last (forced) encoding I used was Japanese, so the Popup for "Säck Subbing Team" showed up as:

Name: S臘k Subbing Team
[...]