Closed Bug 379848 Opened 18 years ago Closed 18 years ago

A dialog window asking to choose encoding pops up after 5 minutes as if the button "Send" was pressed

Categories

(Thunderbird :: Message Compose Window, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 328938

People

(Reporter: beresnyak, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.2pre) Gecko/20061023 SUSE/2.0.0.1-0.1 Firefox/2.0.0.2pre Build Identifier: 2.0.0.0 (20070326) My default encoding for composing messages is Western. If I use characters that do not belong to this encoding, at the time of sending the message, I got a dialog window, asking if I want to send a message in Unicode, or leave it on Western. This is perfectly normal. However, in the new version, this dialog window pops up by itself after about 5 minutes after the "Compose" window was opened, even though I didn't press the "Send" button, often in the middle of composing a message. I suspect that this is due to some auto-save feature. Reproducible: Always Steps to Reproduce: 1. Open Message Compose Window 2. Set Western encoding for the message 3. Enter or paste in some non-western characters 4. Wait for 5 minutes Actual Results: A dialog window pops up, asking which encoding do you want to use to send your message. Expected Results: No window should pop up while you composing the message. The above-mentioned dialog window should appear only when you press the "Send" button.
(In reply to comment #0) > in the new version, this dialog window pops up by itself after about 5 > minutes after the "Compose" window was opened, even though I didn't press the > "Send" button, often in the middle of composing a message. This is also normal. "Dialog window for character encoding" is opened when "Save as draft" in addition to "Send", and "Auto save" feature is enabled as default(5 minutes). See Tools/Options/Composition and check setting in "General" tab.
(Correction of my comment #1) > This is also normal. Issuing of dialog itself is normal when Auto-Save. But "Send in UTF-8"/"Send Anyway"/"Cancel" is not so appropriate when "Save As Drafts", and it's too confusing when non-intentional save, Auto-Save. I've found Bug 328938 for this issue. Sorry for misunderstanding of problem. Question before DUPing to Bug 328938. Will the dialog be displayed even after reply of "Send in UTF-8"?
> Question before DUPing to Bug 328938. > Will the dialog be displayed even after reply of "Send in UTF-8"? No, it won't. Your answer (to change options) basically solves it for me, thank you. Some points to consider in the future: 1. As you mentioned, the text "Send as UTF/Send anyway" is misleading. 2. The options changing the behavior of the program, introduced in a new version, has to be disabled by default, as most users install new versions for bug-fixing and do not want to change the program's interface behavior. 3. As I understand, when I type a message, it is stored internally as a Unicode, why do I have to make decision how it is auto-saved? Auto-save is primarily for recovery, so it is an internal matter for the program. The program must always auto-save in Unicode.
(In reply to comment #3) > > Will the dialog be displayed even after reply of "Send in UTF-8"? > No, it won't. Thanks for clarifying. Closing as DUP of Bug 328938. > 3.(snip) > Auto-save is primarily for recovery, so it is an internal matter > for the program. The program must always auto-save in Unicode. Please open new bug(Severity=Enhancement) for your request because "one problem per a bug" is rule, after searching bugzilla.mozilla.org for already opened/dup'ed/wontfix'ed/invalid bugs well. (Off Topic) > 2. The options changing the behavior of the program, introduced > in a new version, has to be disabled by default, as most users > install new versions for bug-fixing and do not want to change > the program's interface behavior. I agree with you. But developers are usually eager to force users to use new feature because he developed it with hard work, so I can't force developers to disable new feature as deafult. See Bug 379086, Bug 272340. See Bug 329018 also.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.