** Observed with 5/10/2000 Win32 build ** This has been broken for a few days and hopefully there is already a bug for it. The pref item: "Edit | Prefs | Mail & Newsgroup | Compsing Messages | default Character Coding" has a drop-down list of charsets but this list widget is reduced to the height of 1 pixel. You can somehow open the drop-down list by mouse-clicking but setting the charset is not reflected in the Mail composer menu. The widget height must be fixed and choosing the charset must be effective.
Nominating for nsbeta2. Can't use this item without fixing the problem. Blocks send charset testing also.
Severity: normal → blocker
I see the same problem in the Font pref popup menu. I see it in release builds (win32 only) but not local debug builds.
Momoi: FYI, this pref is not listed in the new revision of the mail prefs spec. Refer to the spec: http://gooey/client/5.0/specs/mail/Prefs/Preferences.html#Composing I already logged bug #38087 for removal of this pref line from the UI...
QA Contact: lchiang → laurel
Laurel, the spec still contains this item. I think you overlooked it. There is a long standing agreement that this is a must item for PR2. if you look at the illustration, you will see this item udner "Languages" -- I think it is an oversight that the item is listed in the table above. Jennifer added this UI design several days ago. Jennifer, please update the table.
Lest there is misunderstanding about this item, here's the PRD documentation for this I18n feature: http://client/seamonkey/prd/beta2criteria.html#I18N Mail See "Mail/News - I18N Prefs" section.
UE spec updated.
Yes, I see the item has now been added to Message Display since the last revision I worked with. I'll change pref ui bug(s) accordingly.
Target Milestone: --- → M17
Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may pull this for PR2.
Is this still happening?
The dropdown is now visible and functional to select. There is no default shown, however, when initially launching the prefs dialog. Will check to see if there's an existing bug for that and if not will log it as a separate issue. OK using 2000-05-18-08 m16 commercial builds, mac OS 9.0, linux rh6.0 and NT 4.0
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.