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

Issue 626847 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

headless protocol: /json/new won't create a new tab

Project Member Reported by paulir...@chromium.org, Jul 8 2016

Issue description

Perhaps this is just a known limitation? If so, let's get it documented.
 
Owner: alexclarke@chromium.org
fixed by https://codereview.chromium.org/2119063002/ ?
For headless shell I don't think we're planning on supporting the webserver that implements /json/new, although I'd imagine chrome.exe --headless would have it by default.

Instead we have the new Browser.createTarget and Browser.createBrowserContext devtools protocol commands implemented by that patch. NB I think the ability to have isolated request contexts will be useful for webdriver style testing since it's very much easier now to open a tab with known state.
Cc: pfeldman@chromium.org
Gotcha. So you support this at the protocol level. 
We (Lighthouse) can work with this.

Pavel mentions it is probably worth it to support the /json/new endpoint, mostly for backwards compatibility. Telemetry and other protocol users will expect it. He indicates it may be quite straightforward: e.g. kicking off createTarget from the delegate.
Status: Fixed (was: Untriaged)
I *think* we have everything necessary for tab creation in the protocol now.
Cc: altimin@chromium.org eseckler@chromium.org alexclarke@chromium.org skyos...@chromium.org
 Issue 674034  has been merged into this issue.

Sign in to add a comment