853523 - Selecting a Character Encoding through AppButton throws a ReferenceError: SetForcedCharset is not defined

Status: RESOLVED DUPLICATE of bug 851173

(Thunderbird :: Toolbars and Tabs, defect)

Description

[Alexander L. Slovesnik]

Attachment: Screenshot of bug

STR:
1) Select some message.
2) Try to change Character Encoding of this message.

Expected result: Encoding changed
Actual result: Error "ReferenceError: BrowserSetForcedCharacterSet is not defined".

Please note, that this error is shown only when Character Encoding is selected through AppButton. "View -> Character Encoding" works fine.
I've tested it in Thunderbird 20 beta, but some users claim it existed as early as Thunderbird 16. https://getsatisfaction.com/mozilla_messaging/topics/referenceerror_browsersetforcedcharacterset_is_not_defined is 3 months old.

Comment 1

[vvs]

But...
 character Encoding is selected through MAIN MENU -> View -> Encoding works fine!

On AppButton menu -> View -> Encodind -> Encoding name there is no checkbutton!

Comment 2

[vvs]

On AppButton menu -> View -> Encodind -> Encoding name there is no displayed check.

Comment 3

[Daniel Veditz [:dveditz]]

I get this also using Thunderbird 17.0.4 when using the View sub-menu of the toolbar button. On windows the true/old menu bar is hidden but if I expose it through Alt-V that version of the Character Encoding menu works

Not sure if this is the same underlying bug or a different one: If I am viewing the source of a message (Ctrl-U) and try to change the character encoding from the View menu I get an alert dialog that says

[Exception... "Component returned failure code: 0x805e0006 [nsIWebNavigation.reload]"  nsresult: "0x805e0006 (<unknown>)"  location: "JS frame :: chrome://global/content/bindings/browser.xml :: reloadWithFlags :: line 103"  data: no]

Comment 4

[Alexander L. Slovesnik]

Looks like it's dupe of Bug 851173 which has been fixed today.