87822 - Unable to view a different character coding in Composer

Status: VERIFIED INVALID

(Core :: Internationalization, defect)

Description

[Peter Jeziorek]

1) Install the latest build of Netscape 6 (trunk or branch)
2) Type some Japanese characters into the composer
3) Try to change the character coding by clicking on View | Character Coding
4) Notice that all choices are greyed out

Comment 1

[Peter Jeziorek]

adding smoketest to keywords

Comment 2

[Peter Jeziorek]

Greys out on latest Linux build, but works on Mac.

Comment 3

[Peter Jeziorek]

If you edit a page, for example: http://www.yahoo.co.jp/index.html
click on view | character coding, all the options are available to choose from.

If you edit a new page, and try to view | character coding, all the options are
available. Once you type things in, in any language, all the options are greyed out.

Same for Mac. Changed platform and OS to all.

Comment 4

[Asa Dotzler [:asa]]

Browser General is  a bad place to file bugs.  It just means the bugs sit around
a little bit longer before they get assigned to the correct people/component. 
See http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser and
http://bugzilla.mozilla.org/describecomponents.cgi?product=MailNews for
descriptions of the Browser and MailNews components. 

This bug probably belongs in Intenationalization of Editor. 

Comment 5

[nhottanscp]

Disabling the menu is intentionally done.
I think Roy has a bug to enhance the usability of the menu, reassign to him.
Probably, this should be marked as a dup of that bug.

Comment 6

[Teruko Kobayashi]

Changed QA contact to [e-mail].

Comment 7

[Yuying Long]

According the spec of Editor Character Coding Menu:
http://mozilla.org/projects/intl/uidocs/editorcharmenu.html 
> The charset menu will be disabled in all cases in the Editor except when 
> the document is not dirty (i.e. just saved, just opened, or just reloaded 
> -- with no further input). 

Isn't that supposedly the correct behavior?

cc: [e-mail]

Comment 8

[Katsuhiko Momoi]

Yes. This is according to the spec. 
If you want to change the encoding after you
made input into it, then you can always 
do "File | Save as" and save into a different
encoding.
We can potentially not disable the menu and
throw up a dialog but when we implemented it
first, we decied against it since most users
will stick to the default encoding in
editing. 
By the way, we allow changing of encodings 
when no input has been made. The menus may not
be building currently and therefore may not be 
choosable -- i.e. menu cache bug, but when
the menus are available, it can be changed as
long as no input has been made.

Resolving as invalid.   

Comment 9

[Yuying Long]

Verified as invalid.