Closed Bug 23083 Opened 26 years ago Closed 26 years ago

HTML source display window responds incorretly the encoding switching

Categories

(Core Graveyard :: Embedding: ActiveX Wrapper, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jshin, Assigned: jbetak)

References

()

Details

This bug is related to the bug 12502, but is a separate problem. When I change the encoding in the page source display window using View|Character Set menu, the page source display window interpretes HTML and renders the page in question as a web page instead of displaying the HTML source in the encoding specified via View|Character Set menu.
Do we need a charset menu in the View | Source window? I really thik we should settle this question first.
Status: NEW → ASSIGNED
Target Milestone: M13
Target Milestone: M13 → M14
Move to M14
Change the platform and OS to ALL
OS: Linux → All
Hardware: PC → All
reassign to jbetak since I also ask him to take a look at view source issue.
Assignee: ftang → jbetak
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
This should be fully addressed by the fixes I have working in my private tree. I will check them in on Sunday or Monday (02/14) - code review permitting. I made the view-source attribute sticky, so a webshell cannot return to the HTML browsing state, once it's been used for viewing the source of a web page. Also, the attribute is now set whenever a URL is loaded instead of doing it in DocumentReload, which allows us to display the source of web pages without the charset meta tag. The only open point about this problem is, whether a webshell should be used for normal browsing, once the source view is not needed anymore. This could be done by looking at the DTD Document attributes, if deemed useful. Tentative target: after Beta1.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
QA Contact: cpratt → jshin
reopen bugs which have NOT YET FIXED yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
Ok, next attemot to close this bug. The code changes are finally in. They should be in the nightly build on Feb 23.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: --- → FIXED
I tried the newest nightly build(March 1st) and seems like everything works fine.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.