Closed Bug 176992 Opened 24 years ago Closed 21 years ago

Page content generated by document.write() turns blank on reload if meta charset is specified

Categories

(Core :: Internationalization, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: kazhik, Unassigned)

References

Details

(Keywords: intl, Whiteboard: [adt3])

Attachments

(1 file)

Page content generated by document.write() turns blank on reload if charset is specified in META element. Testcase: http://bugzilla.mozilla.gr.jp/showattachment.cgi?attach_id=1268 Original report in Bugzilla-jp: http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=2746
Same on MAS 9.1 Build 2002102508 Target to ALL ?
Keywords: intl
QA Contact: ruixu → ylong
OS: Linux → All
Hardware: PC → All
Summary: Page content generated by document.write() turns blank on reload → Page content generated by document.write() turns blank on reload if meta charset is specified
Blocks: 157673
I think page contents generated by JavaScript are internally treated as utf-8 on Mozilla. Steps: 1. Open the testcase and click. 2. Reload. Page turns blank. 3. Change View -> Character Coding to UTF-8. It's displayed correctly. This behavior is bad. In other than utf-8, contents like this will break on reloading.
Attached file Testcase —
Another testcase that verifies the UTF8 theory.
Nominate as nsbeta1.
Keywords: nsbeta1
>if charset is specified in META element. then... don't do it. so... we probably ignore the META tag the first time we hit it if it is generated from JavaScript. We probably does not "remember" that information so when we hit reload or view source it forgot to "ignore" I think this is adt3
i18n triage team: nsbeta1+/adt3
Assignee: yokoyama → ftang
Keywords: nsbeta1 → nsbeta1+
Whiteboard: [adt3]
ftang
Status: NEW → ASSIGNED
what a hack. I have not touch mozilla code for 2 years. I didn't read these bugs for 2 years. And they are still there. Just close them as won't fix to clean up.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Mass Re-open of Frank Tangs Won't fix debacle. Spam is his responsibility not my own
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Mass Re-assinging Frank Tangs old bugs that he closed won't fix and had to be re-open. Spam is his fault not my own
Assignee: ftang → nobody
Status: REOPENED → NEW
This can be reproduced with Mozilla 1.7.5, but can't be reproduced with 2004111305-trunk/FreeBSD at the latest. Marking WFM.
Status: NEW → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: