Install addon prompt "Add" button can be ambiguous
Categories
(WebExtensions :: Frontend, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: haik, Unassigned)
Details
Attachments
(1 file)
640.38 KB,
image/png
|
Details |
The webextension install doorhanger, with options to either "Cancel" or "Add", can be ambiguous about what is being added. I think it would be more clear (and safer) if the Add button was changed to "Add Extension".
As an example, with the Facebook Container (screenshot attached), the dialog begins with the text "Add Facebook Container" and the button text is "Add" which might lead the user to think a container is being installed (because containers are a Firefox feature), but what is really being added is a webextension named "Facebook Container". Since the dialog starts with "Add <extension name>" and we don't clarify an extension is being added, the extension name can be used to distract/confuse the user about what is actually happening. The dialog lists the permissions such as "Access your data for all websites", but I believe most users skip over those warnings and focus on the Add or Cancel buttons.
In short, the "Add" button is always in agreement with the "Add <extension name>" header even when the extension name implies something other than an extension is being added.
Comment 1•6 years ago
|
||
Added needinfo assigned to Philipp to get this into his radar (and marked the issue as P3 in the meantime, to take it off from our weekly triaging).
Comment 2•6 years ago
|
||
Thanks! I'm not opposed to these changes, but I'd like to check with our UX team to see if this aligns with their plans. I've put this into our planning.
Updated•6 years ago
|
Though I'm not a native speaker, I propose to use the word "install" instead. To me "add" is rather to be used for atomic actions but setting the extension into a browser is a complex action that can change a lot of look and behavior. On acceptance of my proposition, it should be changed in AMO too.
Updated•3 years ago
|
Description
•