12502 - View Source doesn't display non UTF-8 charsets on doc's w/o HTTP or Meta

Status: VERIFIED FIXED

(Core :: Internationalization, defect, P3)

Description

[Frank Tang]

It work currently when the HTTP header charset present. We have a seperate bug
when the HTML Meta charset present (and assign to harishd). But we also need to
do this when only Deftault encoding is there.

Comment 1

[Frank Tang]

Mark this Assigned M11

Comment 2

[Frank Tang]

mark M12

Comment 3

[Frank Tang]

When we launch view source window. We should copy the charet of the docuemnt and 
set it as the default charset for the view-source window. I don't know how to 
pass that information. Reassign to jbetak to study.

Comment 4

[leger]

Putting on PDT- radar for beta1.  Need for RTM, but would not hold for beta.

Comment 5

[Frank Tang]

I don't think this is a beta stoper. We need to fix the charset menu for the 
view source. That is beta stopper. But I don't think this is a beta stoper. 

Comment 6

[[e-mail] (away - not reading bugmail)]

View source should be now in an acceptable shape for Beta1. We still don't 
transfer the current charset settings from the "parent" browser window to the 
view source webshell. I looked into the code and I think it might be saner to 
address this in the light of a "larger" solution. Both bug 27646 (transfer 
charset settings to new "child" webshells) and bug 21313 (document charset 
caching) might offer a very good way to solve the problem in a more general 
way, instead of layering even more view-souce-specific hacks...

Comment 7

[Frank Tang]

reopen bugs which have NOT YET FIXED yet.  

Comment 8

[Frank Tang]

Change the summary to "View Source doesn't display non UTF-8 charsets on doc's 
w/o HTTP or Meta" to reflect the reality. Currenlty View source fallback to 
UTF-8 not ISO-8859-1.

Move this bug to M15.

Comment 9

[Frank Tang]

*** Bug 23577 has been marked as a duplicate of this bug. ***

Comment 10

[jmmrb]

Attachment: Can't see the entire source to this HTML, BI 2000021516 (WNT 4.0)

Comment 11

[[e-mail] (away - not reading bugmail)]

Requesting PDT+ status and permission to check-in a private fix for Beta1. The view source 
functionality is currently broken in a way that will be quite prohibitive to effective testing, 
problem tracking and will very likely significantly impact Beta support lines.

Currently, Seamonkey is not capable of displaying the source of a large percentage of web pages. 
On top of that any user interaction with the view source window will lead to a fall-back to regular
HTML page rendering instead of the HTML source.

Potential risks are limited to XML: if we missed something in our fix, the 
view source for XML instead of HTML documents might be broken

Comment 12

[[e-mail] (away - not reading bugmail)]

Ok, next attemot to close this bug. The code changes are finally in. They should be in the nightly build on Feb 23.

Comment 13

[Teruko Kobayashi]

I verified this in 2000022308 Mac and Linux, and 200002309 Win32 build.