Closed
Bug 652988
Opened 14 years ago
Closed 7 years ago
Passwords API should not throw nsIExceptions
Categories
(Add-on SDK Graveyard :: General, defect, P2)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: wbamberg, Unassigned)
References
Details
See bug 646865 comment 5.
> High-level Jetpack APIs should not be exposing nsIFoos.
> This should be a standard JavaScript Error object.
Reporter | ||
Comment 1•14 years ago
|
||
Updated•14 years ago
|
Priority: -- → P3
Target Milestone: --- → 1.0
Comment 2•13 years ago
|
||
(automatic reprioritization of 1.0 bugs)
Priority: P3 → P2
Target Milestone: 1.0 → 1.1
(Pushing all open bugs to the --- milestone for the new triage system)
Target Milestone: 1.1 → ---
Bug 646865 was fixed a few hours after comment 1 was made, back in April.
Will, is this still needed?
Reporter | ||
Comment 5•13 years ago
|
||
Hey Wes
Yes: or at least, it's not invalidated by bug 646865 being closed. 646865 was a docs bug; this bug came from an observation Drew made about the Passwords API: that it should not expose internal nsI* objects. FWIW I agree with this.
I suppose fixing it now is a compatibility break, so we might choose to WONTFIX it, and we have a lot of bugs that are more serious, but it does seem to me a valid bug still.
Updated•12 years ago
|
Assignee: erikvvold → evold
Updated•12 years ago
|
Assignee: evold → nobody
Comment 6•7 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•