78962 - Cannot change the Character set in Sidebar

Status: RESOLVED INVALID

(SeaMonkey :: Sidebar, defect)

Description

[Teruko Kobayashi]

"Visual Town" page in Sidebar does not contain meta-charset info, so Japanese 
characters in the page is displayed as garbage.

Steps of reproduce
1. Click on Tabs ->Customized Sidebar in Sidebar 
2. Select "Visual Town" from "Available Tab" and click "Add" button
3. Click "OK" button to close Customized Sidebar dialog
4. Look at "Visual Town" in Sidebar

Japanese characters are displayed as garbage.  The page does not contain 
meta charset info.

I changed Character set menu in Browser to Japanese (EUC-JP) or changed default 
charset to Japanese (EUC-JP), the page in the side bar does not effect.

Tested 2001-05-04-04 Win32, Mac, and 05-04-05 Linux build.

Comment 1

[Linda Baliman]

This is a content bug and appears to be a dup of Bugscape 3226

Comment 2

[Teruko Kobayashi]

Bugscape 3226 is the content bug, but sidebar should be able to change the 
character set someway. 

Comment 3

[Asa Dotzler [:asa]]

Can someone please tell me why this bug is marked Netscape Confidential? 
Netscape Confidential is reserved for security bugs only. Please remove the
confidential flag unless you can show me some piece of this report that covers a
security vulnerability.  Thanks.

Comment 4

[Viswanath Ramachandran]

nav triage: we're not going to hold m0.9.4 for this but would like to get this 
in mozilla0.9.5 or later. adding Jaime to Cc also. 

Comment 5

[Andreas Becker]

mass change, switching qa contact from jonrubin to ruixu.

Comment 6

[matt]

This page looks the same in the content area and the sidebar
http://www.visualtown.com/software/nscape/index.html

I do observe that when the char. encoding is manually switched the sidebar does
not switch.   This would require that the sidebar frame be updated also
with the same charset.   Right now i believe this updating happens in embedding
but we can also do it in the frontend I believe.  I think a function called
BrowserSetForcedCharacterSet does this.

Comment 7

[Jaime Rodriguez, Jr.]

This has been around since May, and my assumption is that we shipped early
verisons with it.

Comment 8

[Asa Dotzler [:asa]]

0.9.5 is out the door. bumping TM up by one.

Comment 9

[Samir Gehani]

Taking.

Comment 10

[Vedran Miletic]

retargeting

Comment 11

[wkfx2003-bugzilla]

Still here....I personally hope this get implemented...

Comment 12

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 13

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 14

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 18

[Karsten Düsterloh]

Content bug - the sidebar is not meant to replace the browser.