19.25 KB, image/jpeg
The view of the source of http://www.thirdnipple.com/mozilla/charset.xml is corrupt (download the file to compare).
Is this linux only? Do we have any known bugs for view source?
This is not a problem with Windows build -- 8/23/2000. But I think we may have a problem in reflecting charset info in XML files. I don't see a correct charset checkmark on this file even though it should be ISO-8859-2.
momoi: we do have that problem, see bug 50107.
Created attachment 13428 [details] Screen shot of view source using build id 2000082308. Is this broken?
Yes. It was worse, actually, when I tried it last time (it didn't print anything after "sama sr") but this time the error is that the E in <!ELEMENT ...> is missing, which is really weird.
Reassign to Frank.
Assignee: nhotta → ftang
hum... When do we start to support View Source for XML ? Part of the problem is in 41981.
Change the summary from "View Source broken with ISO-8859-2 character set" to View source for XML is broekn with on non UTF-8 page which specified by <?xml encoding="" .
Summary: View Source broken with ISO-8859-2 character set → View source for XML is broekn with on non UTF-8 page which specified by <?xml encoding=""
Sounds like it would be... I think, btw, that the <!ELEMENT ... > missing the initial "E" in the view source is a different bug...
I think this is related to 41981. When we view XML page, we display right, but we didn't pass that info into nsIDocument. And when we view source, we stillt think that document is in UTF-8 because nsIDocument say so.
Changed QA contact to firstname.lastname@example.org for now.
QA Contact: teruko → andreasb
The url somehow redirect to a porn site now. :( I think this problem is gone for labeled page. The problem seems still exist for no label (utf-8) page.
whoa, sorry about that. my registration of thirdnipple.com expired. fixing the url. also, ftang is right -- this seems to be fixed :) resolving wfm.
Changing QA contact to teruko.
QA Contact: andreasb → teruko
Verified as worksforme.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.