Skip to content

Add browser/Chrome ecosystem domain group for browser-testing projects #21643

@Mossaka

Description

@Mossaka

Problem

deno/fresh (and potentially other browser-testing projects) need Chrome/Google domains for integration tests that launch headless Chrome. 81 requests were blocked in v6.

Blocked Domains

  • accounts.google.com (20 requests)
  • www.google.com (24 requests)
  • fresh.deno.dev (10 requests)
  • optimizationguide-pa.googleapis.com (16 requests)
  • redirector.gvt1.com (3 requests)
  • safebrowsing.googleapis.com (2 requests)
  • update.googleapis.com (6 requests)

Suggested Implementation

Add a browser or chrome ecosystem domain group:

  • *.google.com
  • *.googleapis.com
  • *.gvt1.com
  • fresh.deno.dev (Deno-specific)

This would benefit any project using headless Chrome/Puppeteer/Playwright for testing.

Evidence: v6 build-test experiment, deno/fresh workflow run.

Metadata

Metadata

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions