Closed
Bug 538931
Opened 15 years ago
Closed 8 years ago
Cancelling the New Account Wizard after being triggered from "Write" button should close the write window.
Categories
(Thunderbird :: Account Manager, defect)
Thunderbird
Account Manager
Tracking
(blocking-thunderbird3.1 -)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
blocking-thunderbird3.1 | --- | - |
People
(Reporter: standard8, Assigned: dmosedale)
References
Details
As per bug 524863 comment 21 through 23: > There's the following problem with Patch v2: > > Prior to this patch landing, dismissing the account setup dialog, that appears > after clicking the Write button (i.e. you've still elected not to setup an > account), would make the Write dialog also disappear. > > With this path, however, the Write dialog remains. This makes no sense, since > it's not really usable: (1) impossible to type in the message pane; (2) > impossible to save. If one leaves that Write dialog open and again clicks the > Write button, this process can be repeated, leaving many Write dialogs open. > > I believe the Write dialog should be dismissed as before. I know we can assume > no user will ever be that thick, but do we really want to go there? :-) Attachment 413848 [details] [diff] has a draft patch for this (which was suggested to get in for 3.1).
Flags: blocking-thunderbird3.1?
Comment 1•14 years ago
|
||
Not a blocker since this is a relatively rare use case.
blocking-thunderbird3.1: --- → -
status-thunderbird3.1:
--- → wanted
Flags: blocking-thunderbird3.1? → blocking-thunderbird3.1-
Reporter | ||
Updated•14 years ago
|
status-thunderbird3.1:
wanted → ---
Flags: wanted-thunderbird+
Comment 2•13 years ago
|
||
Did this somehow become fixed in trunk? This is WORKSFORME. (Clicking "Cancel" on Account Wizard -- and then confirming ("Exit") in the dialog that pops up -- closes both the Account Wizard and the Write window that triggered it) Mozilla/5.0 (X11; Linux x86_64; rv:7.0a2) Gecko/20110720 Thunderbird/7.0a2
Comment 3•13 years ago
|
||
Ah -- per bug 524863 comment 28, it appears that that bug's patch (which caused this bug on the 3.0 branch) simply never landed on trunk, which is why this is WORKSFORME on everything post-3.0.
Comment 4•8 years ago
|
||
-> WFM.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•