Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streamline and optimise after-install dialog action buttons #199

Open
carlosjeurissen opened this issue Apr 14, 2022 · 0 comments
Open

Streamline and optimise after-install dialog action buttons #199

carlosjeurissen opened this issue Apr 14, 2022 · 0 comments
Labels
inconsistency Inconsistent behavior across browsers

Comments

@carlosjeurissen
Copy link
Contributor

Background

The behavior when an extension is installed differs per browser. Google Chrome and Mozilla Firefox open a small dialog in the top right corner informing the extension has just been installed. See attachments.

Google Chrome will close this dialog when a new tab is opened either by the user or the just installed extension. While Mozilla Firefox keeps it in view.

Mozilla Firefox provides an option to use the extension in private windows while other browsers don't.

Apple Safari doesn't currently show such dialog. However, when additional permissions are needed, it will show such popup with repeated permission questions.

Proposals

Keep the dialog in view even when tabs are opened.

This prevents extensions from hiding the dialog and allows extensions to open an on installed tab while preserving this dialog which could include important options.

Allow to pin the extension right from the start

If an extension defined it likes to be pinned right from the start (see #198) or if a browser wants this option to be available at all times. An option to the dialog could be added to pin the extension on the navbar or add it to other parts of the UI.

Grant core permissions

Some browsers do not grant specific non-optional permissions defined in permissions or host_permissions right from the start. However, those permissions could be core to the functionality of the app. The on-installed dialog could allow the user to grant / ungrant certain permissions which the extension author claims to be core to their functionality.

Bringing it all together

Depending on which features browsers decide to implement it could look something like this:
installed-dialog

Attachments

firefox-install-dialog

chrome-install-dialog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inconsistency Inconsistent behavior across browsers
Projects
None yet
Development

No branches or pull requests

2 participants