Users can configure or disable specific notification types
Why it matters
Notifications that fire unconditionally — with no user-facing toggle to silence them — violate the Chrome Web Store User Data FAQ expectation that users control communication from installed extensions. A user who wants daily summaries but not real-time alerts has no recourse except disabling notifications at the OS level, which also silences other apps. This drives uninstalls and triggers Chrome Web Store policy review flags for pushy or invasive behavior, and makes the extension non-compliant with enterprise deployment policies that require per-feature user control.
Severity rationale
High because users cannot silence unwanted notifications without OS-level action, driving uninstalls and review penalties.
Remediation
Add per-category notification toggles to the options page and have the background worker check chrome.storage.local preferences before every chrome.notifications.create call. Wire the checkboxes in options.html and guard dispatch in background.js:
chrome.storage.local.get(['notifPrefs'], ({ notifPrefs = {} }) => {
if (notifPrefs.alerts === false) return;
chrome.notifications.create({ /* ... */ });
});
Include at minimum a master toggle plus one toggle per notification category.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Extension UX & Performance Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from extension-ux-performance·automated