Closed
Bug 283684
Opened 19 years ago
Closed 19 years ago
Freeze nsIPrefBranch2
Categories
(Core Graveyard :: Embedding: APIs, defect)
Core Graveyard
Embedding: APIs
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
Followup to bug 281414, actually freeze nsIPrefBranch2 before 1.8b2.
Comment 1•19 years ago
|
||
it's ready. slap a patch in here that makes it so, and i'll give you my blessings. any thoughts on patching the 1.7 branch? it'd be nice to at least have a Gecko SDK (usable with Firefox 1.0) that reflected the availability of this interface, but given the name change that might be awkward and confusing. hmm...
Comment 3•19 years ago
|
||
counter proposal are welcome, but I didn't see any response to bug 281414 comment #12?
Comment 4•19 years ago
|
||
Well, if the name has to refect the fact that it derives from nsIPrefBranch, you're stuck with nsIPrefBranchSomething, and that makes sensible names hard to come up with. Even so, I'd vote for nsIPrefObservers.
Comment 5•19 years ago
|
||
But, it doesn't really make sense to call getBoolPref, for example, on an interface named nsIPrefObservers. We're looking for an interface name that subsumes all of nsIPrefBranch + Add/RemoveObserver.
Assignee | ||
Comment 6•19 years ago
|
||
I don't know exactly when this actually got done, but the @status FROZEN is in the IDL now.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•