Gary Liu Reporter
	Description • 24 years ago

This bug is related to bug 45059. Specifically, when viewing a message with an 
incorrect MIME charset info in the main window (the 3-pane view), one can 
change the view->character coding setting so that the message will be displayed 
correctly. After making this change, when the message is opened up in a 
standalone window, it should be displayed correctly if the change has been 
inherited by the standalone window. However, the standalone window does not 
currently inherit the changes made in the main window.
  
observed with 2000-08-16-08M18 build
 
Steps to reproduce:
1. in the main window view a message with false/missing MIME charset info so 
that it's not displayed correctly. 
2. go to View->Character Coding and select the correct language so that the 
message is displayed correctly.
3. double click on the message to open it in a standalone window.

expected result: message should be displayed correctly in a standalone window 
using main window's new charset setting.

actual result: message is not displayed correctly because standalone window 
fails to inherit the charset change made in the main window.

	nhottanscp
	Comment 1 • 24 years ago

Confirm the bug.

	nhottanscp
	Comment 2 • 24 years ago

Reassign to mscott.

	Scott MacGregor
	Comment 3 • 24 years ago

I don't think this meets our beta3 criteria. Moving to future. Feel free to take
it up with mail triage team if we need to look at it more.

You can always just change the charset in the standalone message pane and we
display the message correctly. 

	scottputterman
	Comment 4 • 24 years ago

marking nsbeta1+ and moving to mozilla0.8

	Katsuhiko Momoi
	Comment 5 • 24 years ago

QA contact to marina.

	scottputterman
	Comment 6 • 24 years ago

moving to mozilla0.9

	scottputterman
	Comment 7 • 24 years ago

reassigning to chuang.

	scottputterman
	Comment 8 • 24 years ago

moving to mozilla0.9.1

	scottputterman
	Comment 9 • 24 years ago

reassigning to putterman.  I've been working on this a bit and have a partial
solution.  Need to work on the rest.

	scottputterman
	Comment 10 • 24 years ago

moving to 0.9.2

	scottputterman
	Comment 11 • 24 years ago

marking nsbeta1- and moving to future milestone

	marina
	Comment 12 • 23 years ago

added nsbeta1 keyword, it's a good feature to have and it's a common situation
for users to open a stanalone message window.

	nhottanscp
	Comment 13 • 23 years ago

Charset override only has one time effect, not inherited to other window which
is also true for browser. For the convenience to view non MIME, we have folder
charset feature.

	scottputterman
	Comment 14 • 23 years ago

reassigning to ssu.

	Frank Tang
	Comment 15 • 22 years ago

take out Future and nsbeta1-. Change it to --- and nsbeta1 to ask for
consideration of nsbeta1+ for m1.2final

	Simon Montagu :smontagu
	Comment 16 • 22 years ago

we think this is a low priority bug, changed to nsbeta1-

	Samir Gehani
	Comment 17 • 22 years ago

i18n triage team: nsbeta1-

	Clotho
	Comment 18 • 21 years ago

I face this problem frequently as I want to view all HTML with charset Big5 with
Big5-HKSCS (to see some Hong Kong special characters, which are very common). I
need to change the charset page by page, which is unconvenient.

I hope that the charset can be inherited. Or, moreover, it is better than I can
choose to override the MIME charset by my defualt charset.