Closed Bug 556254 Opened 15 years ago Closed 15 years ago

Change default option "Apply default to all message to all messages in the folder..." to NO

Categories

(Thunderbird :: Preferences, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Aureliano, Unassigned)

Details

In bugzilla we have a lots of "bugs" that point to "the original characters were incorrect..." etc. Often this "issue" type is related only to option "Apply default to all message in the folder..." where messages are stored. I don't remember the default value because I'm TB fan from 0.7.x release, but if today the default value is Yes, it's possible without no other regression to change by defaul to NO? Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.2pre) Gecko/20100330 Lightning/1.0b2pre Lanikai/3.1b2pre ID:20100330031754
Pasquale, what is the pref ?
Should be mailnews.force_charset_override But I don't know how this global pref interact with property "Apply default to all message in the folder..." that is defined at folder level (maybe set the init value on all folders on first install?).
Following is answer to a question by Magnus. > http://web.archiveorange.com/archive/v/NhVByoU3oUaiXhmtqglD > The UI for the global pref to override was removed for tb3, > as it's a sure way to shoot yourself in the foot > - the pref is mailnews.force_charset_override. > -Magnus Aureliano Buendía(bug opener): Do you use prefs.js which contains mailnews.force_charset_override=true? (probably it's set by you via UI while you were using Tb 2 or former) Or you use user.js which contains mailnews.force_charset_override=true? Brief history. 1. Global mailnews.force_charset_override=true was introduced for users who receive many mail of wrong charset in mail header. Default is false since initial. 2. Per folder setting for ignoring wrong charset was introduced. Upon folder creation, mailnews.force_charset_override is probably used because it's user's request by global mailnews.force_charset_override=true. 3. As Magnus says, UI to change mailnews.force_charset_override was removed by Tb 3.0. mailnews.force_charset_override itself is not removed yet. Default is still false. Implementation around the force_charset_override is not changed. Only "remove from UI" was done.
>Do you use prefs.js which contains mailnews.force_charset_override=true? Thanks for complete explanation Wada: my issue is related to an very old prefs.js with mailnews.force_charset_override set to true. I try with a new fresh profile without the old prefs.js and I veryfied that TB work as expected (and you explain in comment #3). This bug is Invalid because is my mistake. ;-)
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.