Prefs: UI translating IMAP delete_model value incorrectly.

VERIFIED FIXED in M13

Status

P3
normal
VERIFIED FIXED
19 years ago
14 years ago

People

(Reporter: laurel, Assigned: sspitzer)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Using dec06m12 commercial builds

The values 0 and 1 for delete_model are not being reflected/used in the 5.0
prefs UI in the same manner as used in 4.x.

When you create a new IMAP account in 5.0, the default in UI is selected as
"Move to Trash" and the prefs.js doesn't show the pref line (value is 0).  When
you change the new account's UI setting to "Mark as deleted" the value in
prefs.js is changed to 1.  This is opposite of 4.x usage.

When migrating from 4.x, a 0 or 1 value in the pref will show incorrectly in the
5.0 dropdown because of this switched usage.

1.  Open an IMAP account in 5.0.
2.  Edit|Account Setup. Select the Imap account's server panel.
    Change the dropdown selection in "When I delete a message:" to "Mark it as
deleted". Confirm OK.
3.  Check the prefs.js file for the relating 5.0 server pref (your server number
may be different than the following example depending on your configuration):

      user_pref("mail.server.server1.delete_model", 1);

    Notice the value is 1 whereas this "mark as deleted" selection in 4.x would
have a value of 0.
4.  Change the UI selection to "Move it to the Trash folder". Confirm OK.
5.  Check the prefs.js file and notice the line is not present, value is 0.


Actual result:   UI selections mapping to delete_model values 0 and 1 are
switched in comparison to 4.x usage.

Expected result:  UI selections in 5.0 should map to same pref value as was used
in 4.x.
(Reporter)

Updated

19 years ago
QA Contact: lchiang → laurel
Status: NEW → ASSIGNED
Target Milestone: M13
moving to m13.  accepting. should be easy to fix (once I get to it.)
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Component: Back End → Front End
Resolution: --- → FIXED
fixed.

this was a front end problem, so I changed the component.
(Reporter)

Comment 3

19 years ago
OK using:
2000-01-06-08 mozilla build on linux 6.0
2000-01-06-08 commercial build on NT 4.0
2000-01-06-11 commercial build on mac OS 8.5.1
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.