Closed Bug 555509 Opened 10 years ago Closed 9 years ago

Clicking disable or enable in the detail view doesn't update the UI

Categories

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

defect

Tracking

()

VERIFIED FIXED
mozilla1.9.3a5

People

(Reporter: mossop, Assigned: Unfocused)

References

Details

(Whiteboard: [rewrite])

Attachments

(1 file)

If I go to the detail view of an add-on and click disable/enable nothing appears to happen. Going back to the list shows the change and an ugly progress-bar-like-thing.
Dave, can you attach a screenshot?
Attached image screenshot
Thanks Dave. That's already handled in bug 554245.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 554245
Bug 554245 makes no mention of the disable/enable button having no effect in the list view. That is the main issue here.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
http://hg.mozilla.org/projects/addonsmgr/rev/24f4f87cb241
Whiteboard: [rewrite] → [rewrite][fixed-in-addonsmgr]
(In reply to comment #0)
> If I go to the detail view of an add-on and click disable/enable nothing
> appears to happen. Going back to the list shows the change and an ugly
> progress-bar-like-thing.

The broken status image is still present. I have filed bug 561982.
Landed on trunk as a part of bug 554007
Status: REOPENED → RESOLVED
Closed: 10 years ago9 years ago
Resolution: --- → FIXED
Whiteboard: [rewrite][fixed-in-addonsmgr] → [rewrite]
Target Milestone: --- → mozilla1.9.3a5
I think that should be part of a broader test. I will create Litmus tests for all panes which will also cover this part. What about automation?

Verified fixed with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100514 Minefield/3.7a5pre
Status: RESOLVED → VERIFIED
Flags: in-testsuite?
Flags: in-litmus?
Yea, can be automated too. I think.
Flags: in-litmus? → in-litmus?(vlad.maniac)
(In reply to comment #9)
> Yea, can be automated too. I think.

Blair, is that already covered meanwhile by an automated test?
Covered in existing tests browser_list.js and browser_details.js - no need for a litmus test, IMO.
Flags: in-testsuite?
Flags: in-testsuite+
Flags: in-litmus?(vlad.maniac)
Flags: in-litmus-
You need to log in before you can comment on or make changes to this bug.