Closed
Bug 431247
Opened 17 years ago
Closed 16 years ago
"Get All New Messages" was broken (same action as "Get Mail" on selected account/folder)
Categories
(Thunderbird :: Mail Window Front End, defect)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
VERIFIED
FIXED
Thunderbird 3
People
(Reporter: World, Assigned: mkmelin)
References
Details
(Keywords: regression)
"Get All New Messages" in drop down menu of "Get Mail" won't check all accounts.
Same action as "Get Msgs" on selected account/folder was executed.
Checked with next trunk builds on MS Win-XP SP2.
> Name=Thunderbird Version=3.0a1pre BuildID=2008042403
> Name=Thunderbird Version=3.0a1pre BuildID=2008042703
Note-1: Selection of an account in drop down menu works as expected.
Note-2: "Get Mail" works as expected on selected account/folder(Bug 428620 fixed)
Reporter | ||
Updated•17 years ago
|
Flags: blocking-thunderbird3?
Comment 1•17 years ago
|
||
Yes, I'm seeing this too, and I'm pretty sure it was there even before the fix for Bug 428620 so it's not a result of that fix.
Assignee | ||
Comment 2•17 years ago
|
||
This is a regression from bug 413781.
The "All accounts" doesn't pass a folder to MsgGetMessagesForAccount (duh). It used to have a command="cmd_getMsgsForAuthAccounts", still needs to.
This is why "Get all new...." results in
Warning: reference to undefined property event.target._folder
Source File: chrome://messenger/content/messenger.xul
Line: 1
It was accidentally working before bug 428620.
I'll take care of this in bug 217942...
Assignee: nobody → mkmelin+mozilla
Blocks: 413781
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Keywords: regression
OS: Windows XP → All
Hardware: PC → All
Assignee | ||
Comment 3•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3
Reporter | ||
Comment 4•16 years ago
|
||
"Get All New Messages" worked again as before with following build.
> Version=3.0a2pre, BuildID=2008060203 on MS Win-XP SP2.
VERIFIED.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•