Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
First identify what you are calling an “error overlay.” If a page element is covering a control, handle that element in the test: dismiss a predictable overlay explicitly, or use Playwright’s page.addLocatorHandler() for one that appears unexpectedly. If the screen is an application or development-server error page, investigate the underlying page exception instead of hiding it. Playwright does not document a universal switch for disabling error screens created by arbitrary frameworks.
Identify which kind of overlay is failing the test
“Error overlay” can describe different things, and they do not have the same fix. Before changing the test, decide whether the visible screen is a site element obstructing an interaction, an error screen rendered by the application or its development framework, or Playwright’s own test information shown in a recording. The right response depends on which one you have.
- A blocking page element: a consent notice, modal, popup, or other visible element prevents a click or assertion from proceeding. Handle it as part of the test flow.
- An application or development error screen: the page is displaying an error produced by the app or framework. Inspect the page error and identify the framework before looking for a framework-specific setting.
- A test-status display in a video: Playwright Test can display test information in recorded video through its video
testoption. That is not necessarily an error rendered by the page. See the Playwright TestOptions reference.
The title alone does not identify the framework or the text shown on the overlay. There is therefore no reliable framework-specific instruction to give until you know what generated it.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDismiss a predictable overlay in the normal test flow
If the overlay is expected—for example, a known dialog that appears at a particular point—wait for it and use its ordinary close or consent control before continuing. Playwright’s Page API recommends explicitly waiting for a predictable overlay and dismissing it as part of the normal test flow rather than using a locator handler. This makes the test’s expected interaction visible in the test itself.
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
Here is a minimal JavaScript example using Playwright Test. Replace the URL, accessible name, and button name with the values used by your site:
import { test, expect } from '@playwright/test';
test('dismisses the expected dialog before continuing', async ({ page }) => {
await page.goto('https://example.com');
const dialog = page.getByRole('dialog', { name: 'Cookie preferences' });
await expect(dialog).toBeVisible();
await dialog.getByRole('button', { name: 'Accept' }).click();
await expect(dialog).toBeHidden();
await page.getByRole('button', { name: 'Continue' }).click();
});The example assumes the site exposes a dialog with that accessible name and a button named “Accept.” Use a locator matching the real page. Checking that the dialog is hidden after dismissal can catch cases where the click did not actually clear the obstruction.
For a predictable overlay, keep this handling near the point in the scenario where it appears. Do not treat a known part of the application flow as an unexplained interruption.
Recommended Free Tools
Use a locator handler for an unexpected blocking element
If an overlay appears variably and obstructs test actions, page.addLocatorHandler() can register a handler for a locator that identifies it. Playwright checks the handler before actions that require actionability checks and before auto-waiting assertions when it detects the locator. The handler should make the blocking element go away—for example, by clicking its close button.
Rank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
import { test, expect } from '@playwright/test';
test('continues when an unexpected notice appears', async ({ page }) => {
await page.goto('https://example.com');
const notice = page.getByRole('dialog', { name: 'Temporary notice' });
await page.addLocatorHandler(notice, async (overlay) => {
await overlay.getByRole('button', { name: 'Close' }).click();
});
await page.getByRole('button', { name: 'Continue' }).click();
await expect(page.getByRole('heading', { name: 'Next step' })).toBeVisible();
});Use a locator that identifies the actual overlay, not a broad locator that could match ordinary page content. The handler is useful only if its action reliably removes the obstruction. If a dismiss button is absent or the screen is not a page element the test can interact with, this approach is not a general-purpose way to suppress it.
Understand when the handler runs
A locator handler is not a background observer. It is evaluated around actions and auto-waiting assertions that perform the relevant checks; it is not triggered merely because an overlay appears while the test is idle. If timing matters, or the overlay has a predictable point of appearance, put an explicit wait and dismissal in the test flow instead.
Investigate an application error screen instead of concealing it
A framework’s development error screen may be reporting a real exception in the page. Removing or bypassing that screen without understanding the error can make an end-to-end test appear to pass while the application remains broken. First capture the page error and inspect what happened.
import { test } from '@playwright/test';
test('records uncaught page exceptions', async ({ page }) => {
page.on('pageerror', error => {
console.error('Uncaught page exception:', error);
});
await page.goto('https://example.com');
});Playwright documents page.on('pageerror') as the event emitted when an uncaught exception happens within the page. The Page API also provides page.pageErrors() to retrieve stored page errors and page.clearPageErrors() to clear them. Use these APIs to help investigate the failure; clearing stored errors does not repair the exception or establish that the page is healthy. The relevant reference is Playwright’s Page API.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
Once you know which framework generated the error screen, consult that framework’s documented development configuration if suppressing its overlay is genuinely the goal. The Playwright Page API does not provide a single global option for disabling arbitrary application frameworks’ error overlays. When the screen represents a real page exception, fixing its cause is usually the meaningful test fix.
Use Playwright diagnostics to tell a page failure from an action failure
Read the failing assertion or action message and its call log before changing the test. The failure may show that a target was covered, did not become actionable, or that navigation or page execution failed. Those are different problems: an obstruction calls for handling the page element; a page exception calls for investigating the application.
For additional API-level detail, run the test with Playwright’s documented debugging environment variable:
DEBUG=pw:api npx playwright testThis enables Playwright API debug output while the tests run. The command is documented in the Playwright Debugging Tests guide. Use it alongside the test’s failure message and call log, not as a way to hide the overlay.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
Choose the handling method by predictability
| Situation | Best fit | Why |
|---|---|---|
| The overlay is expected and appears at a known point | Explicitly wait for it and dismiss it in the test flow | Playwright recommends this for predictable overlays; the expected interaction remains clear in the scenario. |
| The overlay is variable or unexpected and blocks actions | Register a locator handler | The handler can dismiss a detected blocking element before an action or auto-waiting assertion proceeds. |
| The screen is an app or framework error page | Inspect page errors and identify the framework | A Playwright locator handler is not a universal framework error-overlay switch; the screen may signal a real exception. |
| The display appears in a Playwright recording | Check the video test option |
A test-status overlay in a video is distinct from an application page element. |
Troubleshooting common failures
The click still times out after adding a handler
Check that the locator matches the visible blocking element and that the handler’s close action succeeds. A handler only helps when Playwright detects its locator at a relevant action or assertion check and the handler makes the obstruction go away. If the overlay is expected, handle it explicitly at its known point instead.
The handler does not run when the overlay appears
This is consistent with the handler’s timing: it does not continuously watch the page in the background. Make the test perform an appropriate action or auto-waiting assertion after the overlay may appear, or use an explicit wait and dismissal when the appearance is predictable.
The page displays a development error screen
Listen for pageerror and inspect the stored page errors. Determine the framework that produced the screen, then fix the underlying error or use that framework’s own documented configuration if suppression is appropriate. Playwright does not establish a universal setting for third-party framework overlays.
The video contains a test overlay, but the page does not
Check the Playwright Test video configuration and its test option. Do not treat a status display in a recording as proof that the application rendered an error element.
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
The failure message is unclear
Review the error message and call log, then run DEBUG=pw:api npx playwright test for additional API-level detail. Use that output to determine whether the issue is an obstructing element, a page exception, or another failure.
Or skip the browser setup
For a screenshot of a page rather than an E2E interaction test, ScreenshotNeo provides a website screenshot API and MCP server. It is not a replacement for diagnosing or fixing an application error screen. Its capture options can accept cookie or consent banners and remove known consent platforms, newsletter popups, and chat widgets before the shot; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses indicate the page verdict and billing status in headers.
One GET request returns an image or PDF. For example, save a WebP screenshot of the target page with cURL:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemscurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo documentation for API details. Its MCP server includes take_screenshot, get_page_info, and capture_pdf for AI agents. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up free for 1,000 screenshots a month, with no card required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
