New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 682703 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
eseckler@chromium.org
skyos...@chromium.org
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Headless: --deterministic-fetch only affects default BrowserContext

Project Member Reported by eseckler@chromium.org, Jan 19 2017 
The command line flag --deterministic-fetch should probably affect all BrowserContexts, e.g. by setting an option on the HeadlessBrowser::Options. 

This is a bit more complicated, since it's realized through ProtocolHandlers, and ProtocolHandlers are owner by individual BrowserContexts.

An alternative might be to add a deterministic-fetch option to DevTools' CreateBrowserContext command.

Comment 1 by eseckler@chromium.org, Jan 19 2017

Labels: Proj-Headless

Comment 2 by eseckler@chromium.org, Jan 19 2017

Labels: HeadlessUpForGrabs

Comment 3 by skyos...@chromium.org, May 15 2017

Components: Internals>Headless
Project Member

Comment 4 by sheriffbot@chromium.org, May 15 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by skyos...@chromium.org, May 16 2018

Status: Available (was: Untriaged)
►

Sign in to add a comment