Silencing alerts automatically vs. logging then dismissing: trade‑off for reducing notification noise in Puppeteer

The Optimal Approach: Log then Dismiss

To balance noise suppression with visibility, the best approach is to log the dialog message and then dismiss it. This ensures you maintain a record of application-level events for debugging while preventing the browser from hanging on a modal dialog.

Comparison of Strategies

Approach	Visibility	Reliability	Risk
Automatic Dismissal	None	High	Masks critical UI regressions or errors.
Log then Dismiss	High	High	Slightly more verbose logs.

Impact on Script Reliability

Puppeteer scripts are synchronous regarding page navigation; a modal dialog blocks the execution of the page. If the page.on('dialog') event is missed or fails to fire, the script will likely hang until it hits a timeout, as the browser remains in a blocked state waiting for user interaction.

It is important to note that page.on('dialog') only intercepts JavaScript-driven dialogs (alert, confirm, prompt). It does not capture browser-level system notifications, such as Service Worker push notifications or permission requests.

Combining with Browser Launch Arguments

You can and should use --disable-notifications alongside a dialog handler. These two mechanisms target different layers of the browser:

• --disable-notifications: Suppresses OS-level push notifications and permission prompts.
• page.on('dialog'): Handles JavaScript window methods.

Using both allows you to eliminate system noise without losing the ability to track application-level alerts.

Implementation Example

const browser = await puppeteer.launch({
  args: ['--disable-notifications']
});
const page = await browser.newPage();

page.on('dialog', async dialog => {
  console.log(`Dialog Message: ${dialog.message()}`);
  await dialog.dismiss();
});

Verification Steps

1. Launch Puppeteer with the --disable-notifications flag and trigger a browser-level notification to ensure it is suppressed.
2. Navigate to a page that calls window.alert('Test') and verify the message appears in your console logs before the script continues.
3. Temporarily remove the dialog handler to confirm the script hangs/timeouts when an alert is triggered.

Diagnostic Detail Needed: Are you encountering specific Chromium-specific notifications (e.g., "Allow location access") that are still appearing despite these settings? This would determine if additional browserContext permissions are required.