Playwright errors in pages being looped may report a wrong occurrence

[janbrasna]

Description

See mozmeao/springfield#412

The results captured might be contaminated by using the same page without requesting new browser.newPage() or subsequent close() cleanup. Perhaps iterating on the outside running individual test()s implicitly described on the inside could isolate that better?

Expected result

[chromium] › specs/newsletter/newsletter-embed.spec.js:62:13 › /en-US/firefox/developer/ page › Newsletter submit failure @newsletter

Actual result

[chromium] › specs/newsletter/newsletter-embed.spec.js:62:13 › /en-US/ page › Newsletter submit failure /newsletter/mozilla/ @newsletter 
[chromium] › specs/newsletter/newsletter-embed.spec.js:34:13 › /en-US/ page › Newsletter submit success /newsletter/security-and-privacy/ @newsletter 
  [webkit] › specs/newsletter/newsletter-embed.spec.js:34:13 › /en-US/ page › Newsletter submit success /about/manifesto/ @newsletter 
  [webkit] › specs/newsletter/newsletter-embed.spec.js:62:13 › /en-US/ page › Newsletter submit failure /contribute/ @newsletter 

Environment

https://github.com/mozilla/bedrock/actions/runs/17912694819/job/50927642425

Steps to reproduce

Some specs quickly scanned for the loop:

search?q=repo:mozilla/bedrock+for+(const+slug+of+slugs)

May need porting something along the lines of springfield#417/files for few of the files.