Question Details

No question body available.

Tags

c# microsoft-edge playwright playwright-dotnet

Answers (1)

July 9, 2026 Score: -1 Rep: 44 Quality: Low Completeness: 80%

NewPageAsync() is where your first visible target is created, but the relevant change in this repro is Channel = "msedge". With that option Playwright launches the installed branded Microsoft Edge, not the Playwright-managed Chromium build, so the Edge 148.0.3967.83 -> 150.0.4078.48 update changes the browser binary being automated even though the C# code is unchanged. Playwright documents Microsoft Edge as a branded browser channel in its browser documentation.

If the test does not require real Edge Stable, remove the channel and use Playwright's Chromium instead:

csharp using Microsoft.Playwright;

using var playwright = await Playwright.CreateAsync();

var browser = await playwright.Chromium.LaunchAsync(new BrowserTypeLaunchOptions { Headless = true // No Channel = "msedge" here. });

var context = await browser.NewContextAsync(); var page = await context.NewPageAsync();

await page.GotoAsync("https://www.google.com"); Console.WriteLine(await page.TitleAsync());

If the requirement is specifically Edge Stable, treat this as an Edge-channel regression: keep that job on a known-good Edge version/channel until Edge or Playwright has a fix. --window-position=-2400,-2400 is only worth trying as a local experiment; do not rely on it as a confirmed Edge 150 Playwright .NET workaround.