Bugzilla

The changes in Bug 1525193 represent a usability regression for users who want to easily access the enable/disable and settings options for extensions.

Feedback on reddit has not been positive: https://www.reddit.com/r/firefox/comments/cbgvdd/extremely_poor_addons_manager_ui_design_in_68/ and the new add-on page is now less usable than the one in Chromium (screenshot attached).

I have seen in other bugs that there is a revamp of the add-ons UI coming, but the direction this seems to be going in today seems to be a step backward, and feels more like form over function.

Chromium, for example, allows for removal and enabling/disabling without needing a kebab menu.

Even if the add-on details view that appears had disable/enable/remove buttons, that would be a marked improvement over the current UI - why does it need to be hidden behind a kebab menu?

As it is, if a user is trying to test whether some add-ons are causing issues with the browser -- and they know it is likely an add-on because safe mode works -- they must click, then use a menu and click again *for each add-on* that they want to disable. 

Previously, they could simply click once in a disable button that didn't require navigating a menu (not the easiest thing to do if a user has motor control issues, for example).

Has this been tested on users of varying levels of experience? What kind of use cases were tested? It'd be interesting to know whether users who were given a task to disable 4 add-ons preferred the new approach over the old. 

Look at the reddit commentary and please reconsider, or provide users with some assurance that the new revamp will take these issues into consideration.

The changes in Bug 1525193 represent a usability regression for users who want to easily access the enable/disable and settings options for extensions.

Feedback on reddit has not been positive: https://www.reddit.com/r/firefox/comments/cbgvdd/extremely_poor_addons_manager_ui_design_in_68/ and the new add-on page is now less usable than the one in Chromium (screenshot attached).

I have seen in other bugs that there is a revamp of the add-ons UI coming, but the direction this seems to be going in today seems to be a step backward, and feels more like form over function, or like a mobile UI where there is no progressive enhancement for people with larger screens. 

This isn't even all that touch friendly -- the menus are harder to tap than the previous buttons, and kebabs don't even look like menus at first glance. 

Chromium, for example, allows for removal and enabling/disabling without needing a kebab menu.

Even if the add-on details view that appears had disable/enable/remove buttons, that would be a marked improvement over the current UI - why does it need to be hidden behind a kebab menu?

As it is, if a user is trying to test whether some add-ons are causing issues with the browser -- and they know it is likely an add-on because safe mode works -- they must click, then use a menu and click again *for each add-on* that they want to disable. 

Previously, they could simply click once in a disable button that didn't require navigating a menu (not the easiest thing to do if a user has motor control issues, for example).

Has this been tested on users of varying levels of experience? What kind of use cases were tested? It'd be interesting to know whether users who were given a task to disable 4 add-ons preferred the new approach over the old. 

Look at the reddit commentary and please reconsider, or provide users with some assurance that the new revamp will take these issues into consideration.