Port |Bug 437657 - increase autocompact threshold "mail.purge_threshhold"| to SeaMonkey

RESOLVED FIXED in seamonkey2.1b3

Status

SeaMonkey
MailNews: Account Configuration
--
minor
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: sgautherie, Assigned: InvisibleSmiley)

Tracking

Trunk
seamonkey2.1b3

Firefox Tracking Flags

(blocking-seamonkey2.1 b3+)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
That bug changed TB value unit to MB from KB.

"blocking-seamonkey2.1=?":
As this impacts strings, SM should do it before 2.1b3, if we want to sync' (in 2.1 cycle).
(Reporter)

Updated

7 years ago
Blocks: 360488

Updated

7 years ago
Duplicate of this bug: 636373

Comment 2

7 years ago
> David :Bienvenu      2011-01-12 17:08:48 PST

> Created attachment 503351 [details] [diff] [review]
> turn on autocompact by default, switch to MB
> 
> This patch does several things:
> 
> Turn on autocompact by default
> For TB, migrate the pref to MB, and migrate old pref
> Fix the options UI to use the new pref in MB
> switch the default to 20MB, if the user hasn't changed the threshold.
> 
> This leaves SM using the old pref, but if they fix their preferences UI to use
> MB's, we can turn on the backend code for them.
(Assignee)

Comment 3

7 years ago
So they didn't turn on autocompact just yet, which is good (see below). I don't see any problem with porting the first (prefs/UI) part and removing the ifdefs, though. Karsten?

The reason why I have a problem with autocompacting (and the reason why I turned it off for me eventually after I had it activated for quite some time) is that it seems to throw away the current view, leaving you with an empty thread pane (at least that's what I recall from memory using SM 2.0; I neither checked SM trunk nor Shredder yet). Actually that happens whenever you compact a folder you're currently viewing, but with autocompacting it happens out of the blue (for anyone who doesn't know that it's due to compacting that is, but that's probably the majority of users).
(Assignee)

Comment 4

7 years ago
Created attachment 514808 [details] [diff] [review]
patch [Checkin: comment 6]

Will ask bienvenu for sr once we have an r+.
Assignee: nobody → jh
Status: NEW → ASSIGNED
Attachment #514808 - Flags: review?(mnyromyr)

Updated

7 years ago
blocking-seamonkey2.1: ? → b3+

Updated

7 years ago
Attachment #514808 - Flags: review?(mnyromyr) → review+
(Assignee)

Updated

7 years ago
Attachment #514808 - Flags: superreview?(bienvenu)

Comment 5

7 years ago
Comment on attachment 514808 [details] [diff] [review]
patch [Checkin: comment 6]

cool, thx for getting to this so promptly.
Attachment #514808 - Flags: superreview?(bienvenu) → superreview+
(Assignee)

Comment 6

7 years ago
Comment on attachment 514808 [details] [diff] [review]
patch [Checkin: comment 6]

http://hg.mozilla.org/comm-central/rev/f64fe11636ed
Attachment #514808 - Attachment description: patch → patch [Checkin: comment 6]
(Assignee)

Updated

7 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1b3
(Reporter)

Comment 7

7 years ago
(In reply to comment #3)
> So they didn't turn on autocompact just yet, which is good (see below).

Ftr, iiuc, they did turn autocompact (prompt) on with their (shared) second patch.
No longer blocks: 360488
You need to log in before you can comment on or make changes to this bug.