AskBlocker (eelfgnmggfgncoipinopobfcabnfknho): Blocks overly-eager permission requests for notifications, location, etc. For example, before you've interacted with the page.... Read More > or Download Now >
AskBlocker for Chrome
Tech Specs
- • Type: Browser Extension
- • Latest Version: 1.0.7
- • Price: Freeware
- • Offline: No
- • Developer: adamlynch.com
User Reviews
- • Rating Average
- 3.67 out of 5
- • Rating Users
- 3
Download Count
- • Total Downloads
- 4
- • Current Version Downloads
- 4
- • Updated: March 4, 2018
AskBlocker is a free Developer Tools Extension for Chrome. You could download the latest version crx file and install it.
More About AskBlocker
Block overly-eager permission requests for notifications, location, etc. For example, ones that happen before you've interacted with the page. This was created as part of How to improve your permissions UX (https://adamlynch.com/improve-permissions-ux).
How it works:
Permissions requests are blocked until you've interacted with the page; i.e. click, tap, or key press. Although there are the following exceptions:
- If the permission has been previously requested and granted (or explicitly denied).
- If the domain is `localhost` or `127.0.0.1`.
- If you've navigated to the current page from another page on the same domain.
Things not covered and why:
- Accelerometer, gyroscope, magnetometer, device motion, device orientation, etc. They don't trigger a permissions request popup.
- Ambient light sensor. It doesn't trigger a permissions request popup.
- Bluetooth. This can only be requested due to user interaction anyway (https://webbluetoothcg.github.io/web-bluetooth/#requestDevice-user-gesture).
- Clipboard. It doesn't trigger a permissions request popup.
- Flash. I don't know how the prompt is triggered or how I can intercept this.
- Geolocation's `watchPosition` method. There's no way to achieve this without breaking stuff. It returns an ID and it doesn't offer any way to check the status of the permission, like `Notification.permission`. The Permission API could be used but it's asynchronous (Promise based), so there's no way to use it and also still return the ID.
- Web USB. Not really supported yet (and the Permission API doesn't support it yet), so it probably won't be annoying anyone.
How it works:
Permissions requests are blocked until you've interacted with the page; i.e. click, tap, or key press. Although there are the following exceptions:
- If the permission has been previously requested and granted (or explicitly denied).
- If the domain is `localhost` or `127.0.0.1`.
- If you've navigated to the current page from another page on the same domain.
Things not covered and why:
- Accelerometer, gyroscope, magnetometer, device motion, device orientation, etc. They don't trigger a permissions request popup.
- Ambient light sensor. It doesn't trigger a permissions request popup.
- Bluetooth. This can only be requested due to user interaction anyway (https://webbluetoothcg.github.io/web-bluetooth/#requestDevice-user-gesture).
- Clipboard. It doesn't trigger a permissions request popup.
- Flash. I don't know how the prompt is triggered or how I can intercept this.
- Geolocation's `watchPosition` method. There's no way to achieve this without breaking stuff. It returns an ID and it doesn't offer any way to check the status of the permission, like `Notification.permission`. The Permission API could be used but it's asynchronous (Promise based), so there's no way to use it and also still return the ID.
- Web USB. Not really supported yet (and the Permission API doesn't support it yet), so it probably won't be annoying anyone.
