Opened on 08/19/2015 at 08:16:52 AM
Last modified on 03/14/2016 at 05:51:34 AM
#2926 new change
Support notification opt-out in Internet Explorer
| Reported by: | oleksandr | Assignee: | |
|---|---|---|---|
| Priority: | P3 | Milestone: | |
| Module: | Adblock-Plus-for-Internet-Explorer | Keywords: | |
| Cc: | oleksandr, sergz, greiner | Blocked By: | #2925 |
| Blocking: | Platform: | Internet Explorer | |
| Ready: | yes | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by oleksandr)
Background
We want to give our users the possibility to opt-out from notifications. This has already been implemented in other browsers (See #2193). We want to add that functionality to Adblock Plus for Internet Explorer as well.
What to change
Settings page:
- Add a checkbox to the settings page like shown on the mock-up. It should be hidden by default and only be shown if Prefs.notifications_showui is set to true.
Notification:
- When clicking the "x" on the top right corner of the notification, the notification content should be replaced with the following two links (see screenshot):
- Close this notification: Hide the notification
- Stop showing notifications: Hide the notification and add "*" to Prefs.notifications_ignoredcategories
When a category is added to the list, set the Prefs.notifications_showui to true.
Attachments (1)
Change History (6)
Changed on 08/19/2015 at 08:17:06 AM by oleksandr
comment:2 Changed on 08/19/2015 at 08:21:46 AM by oleksandr
- Blocked By 2925 added
- Cc oleksandr sergz added
- Description modified (diff)
- Ready set
comment:3 Changed on 08/20/2015 at 12:46:13 PM by greiner
- Cc greiner added
comment:4 Changed on 08/20/2015 at 02:15:20 PM by oleksandr
- Description modified (diff)
- Priority changed from Unknown to P3
comment:5 Changed on 03/14/2016 at 05:51:34 AM by oleksandr
- Summary changed from Support notification out-out in Internet Explorer to Support notification opt-out in Internet Explorer
Note: See
TracTickets for help on using
tickets.
The described behavior is inconsistent with how it works so far. Here's the description from #2192 which implemented it in Core: