Build: 01-22 trunk build on all platforms. steps: 1. Launch browser, and go any web page. File | Edit Page to bring the page into Composer. or: 1.Open Composer, type something. 2. File | Save As Charset to bring a dialog. Actually result: There is no charset is highlighted by default. Expected result: There should be one charset is highlighted deponds on the page meta-charset or highlighted as iso-8859-1 if there is nothing specified first in editor page.
Addition info.: The default charset is not highlighted and you can not manually highlight this default charset by click on the charset, mark you feel the charset is not selected. This is a regression between 01-08 and 01-14. Nominate as nsbeta1.
Keywords: intl, nsbeta1, regression
cc cmanske since this is code in mozilla/editor/ui
I would suggest selecting the charset that the current document is using. Note also that if that is selected, then maybe the Ok button should be disabled (no point in trying to change to what it is)?
This is a display problem. I think it got select but we dont' show it. If I select other charset, it will highlight but if I try to select the current one, it won't show the highlight. nsbeta1+ per tirage meeting
Assignee: yokoyama → rchen
Keywords: nsbeta1 → nsbeta1+
By the way, the <tree> used to construct the charset list should now be replaced by the new <listbox> that hewitt finished. It's a lot easier to use and greatly simplifies the XUL! I've used in in EditorPublishSettings.xul, .js if you want to see a simple example.
this is a style sheet issue. we some how does not show the highlight when it IS selected in that part. adt2
Priority: -- → P2
Target Milestone: --- → mozilla1.0
rchen is too busy for the installer bug now. Reassign back to ftang
Assignee: rchen → ftang
Impact Platform: ALL Impact language users: 560M 100% Probability of hitting the problem: MID, Mid workflow Severity if hit the problem in the worst case: Confused the users, User cannot perform the desired action. Way of recover after hit the problem: None. Risk of the fix: Should be very low. Probably only .css file changes. Potential benefit of fix this problem: Probably None ADT3
Priority: P2 → P3
Status: NEW → ASSIGNED
I think the situration got improved. At least now it is possible to select and hightlight the default charset. It will still not pre select the current charset but user CAN select it I think we could nsbeta1- it with the current situration
Keywords: nsbeta1+ → nsbeta1-
Notice this is another new problem that we haven't had before: When you select Save As Charset, it used to point to the current/default charset positon of the charsets list, but now no matter what current/default charset is, the dialog always come up with the charset list from begining (Arabic) even current charset is western, with no charset is highlighted.
work for me now
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
This indeed not in latest trunk build, mark as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.