Closed Bug 552761 Opened 12 years ago Closed 12 years ago

Fix PFS and browser_bug435788.js

Categories

(Toolkit :: Add-ons Manager, defect, P1)

defect

Tracking

()

VERIFIED FIXED
mozilla1.9.3a5

People

(Reporter: mossop, Assigned: mossop)

References

()

Details

(Keywords: regression, Whiteboard: [rewrite])

Attachments

(1 file)

No description provided.
I suspect we already have a litmus test for PFS.
Flags: in-testsuite?
Flags: in-litmus?
Fixed: http://hg.mozilla.org/projects/addonsmgr/rev/43e58a54b4c5
Flags: in-testsuite? → in-testsuite+
Whiteboard: [rewrite] → [rewrite][fixed-in-addonsmgr][needs-review]
Attached patch patch rev 1Splinter Review
This makes the PFS use the new APIs. Some of the confusing wording in the tests is fixed by bug 553022
Attachment #435782 - Flags: review?(robert.bugzilla)
Attachment #435782 - Flags: review?(robert.bugzilla) → review+
Whiteboard: [rewrite][fixed-in-addonsmgr][needs-review] → [rewrite][fixed-in-addonsmgr][needs-landing]
http://hg.mozilla.org/mozilla-central/rev/2683fbcba0fb
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [rewrite][fixed-in-addonsmgr][needs-landing] → [rewrite]
Target Milestone: --- → mozilla1.9.3a5
No orangeness. Marking as verified fixed.

Dave do we need a general PFS test here or a test for a specific area?
Status: RESOLVED → VERIFIED
I think this is covered actually.
Flags: in-litmus? → in-litmus-
You need to log in before you can comment on or make changes to this bug.