Adjust extension button's behavior when there is no active extension
Categories
(WebExtensions :: General, enhancement, P3)
Tracking
(relnote-firefox 145+, firefox145 fixed)
People
(Reporter: willdurand, Assigned: robwu)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [addons-jira])
Attachments
(4 files)
The new extension button introduced in Bug 1777481 should be hidden when there is no visible extension. In order to fully fix this bug, we should listen to some events to know when an extension is added/disabled/removed to make sure the button is only visible when there are visible extensions AND hide this button when there is no visible extension anymore (e.g., the user had only 1 extension enabled and removed it).
Updated•3 years ago
|
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
According to the last UX meeting notes:
DECISION: Should behave like the download button.
- You can right-click the download button and it has a “hide when empty” option
- It stays in the toolbar (keeps its place), but is not visible
- To get it back, you go into customize mode and right click again
- Clicking the Extension button when there are no extensions doesn’t show the panel but instead opens a about:addons tab with recommended extensions
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
while discussing about this bug a few days ago, William and I were wondering if we should also take into account that (if we plan to anchor on the unified extensions button the install flows doorhangers) the unified extension button may also have to become visible when no extension is currently active but there are some in the process of being installed.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 3•3 years ago
|
||
I filed Bug 1781773 for allowing the widget to be customizable, which is kinda related to this bug.
Updated•2 years ago
|
Comment 6•1 year ago
|
||
Small update, we are considering hiding the extension button if user has not installed any extensions.
Comment 8•1 year ago
|
||
This is important in enterprise uses cases as well. For kiosks, locked down machines, etc. with no addons, the button is superfluous.
| Assignee | ||
Comment 9•9 months ago
•
|
||
(In reply to Mike Kaply [:mkaply] from comment #8)
This is important in enterprise uses cases as well. For kiosks, locked down machines, etc. with no addons, the button is superfluous.
The ability to hide the extensions button was enabled in bug 1964857.
Enterprise policies can set extensions.unifiedExtensions.button.always_visible to false to hide the button by default (which ought work ecause the extensions. prefix is permitted here).
What remains here is the default behavior, when no extensions are installed. Currently about:addons is opened when the button is clicked (and when the Extensions Button is hidden, about:addons is opened instead of the panel being shown when the "Extensions and themes" appmenu item is clicked).
What we are going to do is to show some default content that tells the user why no extensions are displayed, where we distinguish between the following cases:
- No extensions installed at all. We distinguish at least between no extensions installed vs extensions installed but disabled (bug 1778684, this bug).
- The window is a private browsing window and none of the extensions have private browsing access (bug 1814871).
These mocks are part of the PRD at: https://docs.google.com/document/d/1Cj_VLH4yGAO7AJh2gUbOLXZVG57Yjpw29RryN_03wp0/edit
From the implementation point of view, I'll start with the last one (bug 1814871) because it would be confusing to show the generic "no extensions installed UI" when the user did in fact do so, but is just in private browsing mode.
Comment 10•9 months ago
•
|
||
Updated•9 months ago
|
Updated•9 months ago
|
| Assignee | ||
Comment 11•7 months ago
|
||
Updated•7 months ago
|
| Assignee | ||
Comment 12•7 months ago
|
||
When bug 1917848 introduced the blocklist messages in the extensions
panel, it added logic to customize the about:addons page that would be
opened if there are no extensions in the panel. It did not include unit
tests for this scenario.
The previous commit in this bug (bug 1778684) defaults to showing the
panel when extensions are disabled, with some explanatory UI. Because
blocklisted add-ons are disabled, this also implies that the
shouldShowBlocklistAttention check in browser-addons.js is now obsolete.
This patch removes that check as a cleanup.
| Assignee | ||
Comment 13•6 months ago
|
||
Comment 14•6 months ago
|
||
Comment 15•6 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/9a23c570cdad
https://hg.mozilla.org/mozilla-central/rev/df293fdfa6ae
https://hg.mozilla.org/mozilla-central/rev/22644b722c56
Comment 16•6 months ago
•
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Change in behaviour when a user clicks the Extensions toolbar button
[Affects Firefox for Android]: No
[Suggested wording]: When a Firefox user has no extensions installed, and clicks the Extensions button on the toolbar, they will now see a message explaining how extensions can elevate their browsing experience with links to the Firefox add-ons store.
[Links (documentation, blog post, etc)]:
Comment 17•6 months ago
|
||
Note added to our 145 beta release notes as well as our draft for our 145 final release notes. I am keeping the relnote flag open until we have shipped the note with 145.0. Thanks.
Description
•