Selecting a Character Encoding throws a ReferenceError: SetForcedCharset is not defined

RESOLVED FIXED in Firefox 12

Status

()

Core
Internationalization
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: blackrazor.qa, Assigned: smontagu)

Tracking

({regression})

12 Branch
mozilla13
regression
Points:
---

Firefox Tracking Flags

(firefox12+ verified)

Details

(Whiteboard: [qa+])

Attachments

(2 attachments)

(Reporter)

Description

5 years ago
Created attachment 594910 [details]
charset_error.docx

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0) Gecko/20100101 Firefox/10.0
Build ID: 20120129021758

Steps to reproduce:

Click View -> Character Encoding -> More Encodings -> East Asian -> Chinese Simplified (GB2312).


Actual results:

A JS error was thrown: ReferenceError: SetForcedCharset is not defined.
(Reporter)

Comment 1

5 years ago
Bug was encountered in FF12/Aurora but filed using FF10. My apologies for any confusion.

Comment 2

5 years ago
Regression window(m-i)
Works:
http://hg.mozilla.org/integration/mozilla-inbound/rev/388edf50e323
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120123 Firefox/12.0a1 ID:20120124003851
Fails:
http://hg.mozilla.org/integration/mozilla-inbound/rev/f173a9a1e056
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120124 Firefox/12.0a1 ID:20120124015351
Pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=388edf50e323&tochange=f173a9a1e056

Suspected: Bug 720310
Blocks: 720310
Status: UNCONFIRMED → NEW
Component: Untriaged → Internationalization
Ever confirmed: true
Keywords: regression
OS: Windows 7 → All
Product: Firefox → Core
QA Contact: untriaged → i18n
Hardware: x86_64 → All
(Assignee)

Comment 3

5 years ago
Ouch, I changed one call to SetForcedCharset to BrowserSetForcedCharacterSet and missed another one 5 lines below even though it's staring me in the face at https://bugzilla.mozilla.org/attachment.cgi?id=590816&action=diff#a/browser/base/content/browser.js_sec1
(Assignee)

Comment 4

5 years ago
Created attachment 594923 [details] [diff] [review]
Patch
Assignee: nobody → smontagu
Attachment #594923 - Flags: review?(gavin.sharp)
Attachment #594923 - Flags: review?(gavin.sharp) → review+
We really should have tests for all of this stuff.
(Assignee)

Comment 6

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/6b3f68d98dcd
status-firefox12: --- → affected
tracking-firefox12: --- → ?
Target Milestone: --- → mozilla13
We need to fix this for 12.
tracking-firefox12: ? → +

Comment 8

5 years ago
https://hg.mozilla.org/mozilla-central/rev/6b3f68d98dcd
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Comment 9

5 years ago
Comment on attachment 594923 [details] [diff] [review]
Patch

[Approval Request Comment]
Regression caused by (bug #): 720310
User impact if declined: Unable to override page encoding in some scenarios
Testing completed (on m-c, etc.): On m-c since 2012-02-08
Risk to taking this patch (and alternatives if risky): None
String changes made by this patch: None
Attachment #594923 - Flags: approval-mozilla-aurora?
Attachment #594923 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(Assignee)

Comment 10

5 years ago
https://hg.mozilla.org/releases/mozilla-aurora/rev/49a2a17edbf6
status-firefox12: affected → fixed
Whiteboard: [qa+]

Comment 11

5 years ago
I have verified this on:

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0 beta 5
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20100101 Firefox/12.0 beta 5
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20100101 Firefox/12.0 beta 5

When following the steps from the description, no error are triggered.
On Ubuntu I've got some warnings but still no error. Is this intended?

Setting resolution to Verified.
status-firefox12: fixed → verified
(Assignee)

Comment 12

5 years ago
(In reply to Vlad [QA] from comment #11)
> On Ubuntu I've got some warnings but still no error. Is this intended?

What warnings exactly?

Comment 13

5 years ago
There are no more warnings on a new profile.
(In reply to Vlad [QA] from comment #13)
> There are no more warnings on a new profile.

Thanks Vlad, can you verify on Firefox 13 as well so we can close this one out?
You need to log in before you can comment on or make changes to this bug.