Wallet should use the newer nsIPrefService APIs instead of nsIPref

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
15 years ago
10 years ago

People

(Reporter: mikael, Unassigned)

Tracking

Trunk
seamonkey2.0a3
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
nsIPref is deprecated
(Reporter)

Updated

15 years ago
Status: NEW → ASSIGNED
Summary: Remove nsIPref from wallet → Wallet should use the newer nsIPrefService APIs instead of nsIPref
(Reporter)

Updated

14 years ago
Assignee: mikael → dveditz
Status: ASSIGNED → NEW
Product: Browser → Seamonkey

Comment 1

13 years ago
I'm a bit of a noob here.
This seems like a hopefully fairly simple bug.

Jesse: I'm not sure this is worth it ...
AFAIK, the wallet module is not used by Firefox or Thunderbird, only Seamonkey.
Eventually the plan is to move Seamonkey to Toolkit, so the entire wallet
extension will be obsolete ...

But no, this is not a simple bug. The Wallet code is horrible and ugly - there
are far better bugs for noobs to take on. 

Take a look at <http://www.mozilla.org/contribute/hacking/first-bugs/>.
Created attachment 195723 [details] [diff] [review]
cleans up nsWalletService.cpp

I'm just posting this here for the sake of trying to get a clean tree.

I do not think I'll fixup wallet any more than this (but maybe), so if dveditz
or someone wants to review this, that'd be cool.
Assignee: dveditz → nobody

Comment 4

11 years ago
(In reply to comment #3)
> Created an attachment (id=195723) [details]
> cleans up nsWalletService.cpp
> 
> I'm just posting this here for the sake of trying to get a clean tree.
> 
> I do not think I'll fixup wallet any more than this (but maybe), so if dveditz
> or someone wants to review this, that'd be cool.
Did you mean to ask for a review on this?
R.WontFix, after bug 473827.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Depends on: 473827
QA Contact: privacy
Resolution: --- → WONTFIX
Target Milestone: --- → seamonkey2.0a3
You need to log in before you can comment on or make changes to this bug.