Closed
Bug 827444
Opened 13 years ago
Closed 13 years ago
Clarify compatibility warning for nsIPrefBranch2
Categories
(addons.mozilla.org Graveyard :: Compatibility Tools, defect)
addons.mozilla.org Graveyard
Compatibility Tools
Tracking
(Not tracked)
RESOLVED
FIXED
2013-01-10
People
(Reporter: davemgarrett, Assigned: basta)
References
Details
+++ This bug was initially created as a clone of Bug #752747 +++
The AMO addon validator has the following warning for usage of nsIPrefBranch2:
------------------------------------------------------------
Warning: This add-on uses nsIPrefBranch2, which has been merged into nsIPrefBranch in Gecko 13. Once you drop support for old versions of Gecko, you should stop using nsIPrefBranch2. You can use the == operator as an alternative.
See bug https://bugzilla.mozilla.org/show_bug.cgi?id=718255 for more information.
------------------------------------------------------------
What exactly does "You can use the == operator as an alternative" mean? nsIPrefBranch2 just provided observer registration prior to being built-into nsIPrefBranch. Did this bit of text get copied accidentally from another warning or am I missing something here? In either case, please clarify the text in this warning.
https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIPrefBranch
https://developer.mozilla.org/en-US/docs/XPCOM_Interface_Reference/nsIPrefBranch2
Comment 1•13 years ago
|
||
Ugh, that was my bad. I must have copied that sentence from a different compatibility warning.
Assigning to Basta, but also adding Kris in case he can produce a quick patch for it.
Assignee: nobody → mattbasta
Target Milestone: --- → 2013-01-10
| Assignee | ||
Comment 2•13 years ago
|
||
Is this just a matter of removing that sentence?
Comment 3•13 years ago
|
||
Yes.
| Assignee | ||
Comment 4•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 5•13 years ago
|
||
Thanks.
Updated•10 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•