Closed Bug 37130 Opened 25 years ago Closed 24 years ago

Implement "Customize..." of Mail Composer charset menu

Categories

(Core :: Internationalization, defect, P3)

Product:
Core
Component:
Internationalization
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: cata, Assigned: jbetak)

References

Details

(Whiteboard: [nsbeta2+][5/16]) 

Step 1: by Juraj [?]
Implement the customization dialog and connect it to the menu item. We should 
reuse the charset menu customization code from Broser.

Step 2: by Cata
Register as listener on the preference and update the menu when that changed.
*** Bug 37403 has been marked as a duplicate of this bug. ***
Reassign to bobj, please assign an engineer for this feature.
Assignee: nhotta → bobj
put nsbeta2
Keywords: nsbeta2
Blocks: 35851
Status: NEW → ASSIGNED
Target Milestone: --- → M16
reassigned to jbetak
Assignee: bobj → jbetak
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
will follow up with Cata, sounds fairly straightforward though...
Putting on [nsbeta2+][5/16] radar.  This is a feature MUST complete work by 
05/16 or we may pull this feature for PR2.
Whiteboard: [nsbeta2+][5/16]
The changes are now in the tree. I followed Cata's suggestion and reused the 
original XUL and JS files from browser charset customization. We are only 
switching the back-end preference string.

This could potentially cause contextual issues, since the UI in this dialog 
currently doesn't change a bit, no matter what menu we put it in. 

The preference service seems to be working now and I feel I can let QA folks 
have a shot at it.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified in 2000-05-22 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.