Closed Bug 1349723 Opened 3 years ago Closed 3 years ago

remove support for standalone about:addons UI


(Toolkit :: Add-ons Manager, enhancement, P3)




Tracking Status
firefox55 --- fixed


(Reporter: rhelmer, Assigned: rhelmer)



(Whiteboard: triaged)


(1 file, 1 obsolete file)

about:addons can be run either in a tab, or in a standalone window.

We run tests for both of these states and it's a burden to maintain. Firefox does not use this, I am not sure about other apps but I don't think there's a reason they could not run in a tabbed browser window instead.

Let's remove tests and any supporting code for the standalone window UI.
See Also: → 1350992
Priority: -- → P3
Whiteboard: triaged
Blocks: 1355998
Please don't forget to remove strings if they're not used anywhere else.
(In reply to Francesco Lodolo [:flod] from comment #6)
> Please don't forget to remove strings if they're not used anywhere else.

Thanks! Looks like there are a few for the tooltips on the back/forward buttons - I'll make sure those aren't used elsewhere and remove them if not.
It's actually turning out to be a little more complex than I'd hoped to remove everything. I am hitting some test failures that are difficult to debug due to the callback depth (12 levels deep in some places!) so I am going to land the basic test removal now to unblock the Screenshots bug 1355998 and do the larger code+strings+remaining tests after.
Keywords: leave-open
Attachment #8866644 - Attachment is obsolete: true
Attachment #8866644 - Flags: review?(aswan)
Comment on attachment 8866594 [details]
Bug 1349723 - remove tests for about:addons UI in standalone window.

::: toolkit/mozapps/extensions/test/browser/browser_bug562797.js:225
(Diff revision 4)
>      });
>    });
>  });
>  // Tests that browsing to the add-ons manager from a website and going back works
>  // Only relevant for in-content UI

this line could go

::: toolkit/mozapps/extensions/test/browser/browser_bug562797.js:400
(Diff revision 4)
>    });
>  });
>  // Tests than navigating to a website and then going back returns to the
>  // previous view
>  // Only relevant for in-content UI


::: toolkit/mozapps/extensions/test/browser/browser_bug562797.js:526
(Diff revision 4)
>    });
>  });
>  // Tests that going back from a webpage to a detail view loaded from a search
>  // result works
>  // Only relevant for in-content UI

and again, several more below

::: toolkit/mozapps/extensions/test/browser/browser_types.js
(Diff revision 4)
> -    is(gBrowser.canGoBack, canGoBack, "canGoBack should be correct");
> -    is(gBrowser.canGoForward, canGoForward, "canGoForward should be correct");

why is this getting removed?
Attachment #8866594 - Flags: review?(aswan) → review+
So. It turns out that `is_hidden` in head.js happens to force a layout flush, which is necessary for one of the later tests which looks at the DOM and tries to pick out the right addon by the element value.

Since we've removed the call to `is_hidden` I've made the layout flush explicit which gets this test passing.
Pushed by
remove tests for about:addons UI in standalone window. r=aswan
Keywords: leave-open
Blocks: 1364333
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in before you can comment on or make changes to this bug.