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

Issue 670870 link

Starred by 3 users
Status: Untriaged
Owner: ----
Cc:
█ manzagop@chromium.org
█ f...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Launching a second browser process should not modify the local state

Project Member Reported by manzagop@chromium.org, Dec 2 2016 
It currently does so on the slow rendez-vous path.

Comment 1 by manzagop@chromium.org, Dec 2 2016

Cc: manzagop@chromium.org
Owner: ----

Comment 2 by manzagop@chromium.org, Dec 5 2016

Labels: -Pri-3 Pri-2
Owner: manzagop@chromium.org
Perhaps we can start by ensuring we have a metric for slow vs fast rdv.

Comment 3 by manzagop@chromium.org, Dec 5 2016

Owner: ----

Comment 4 by wfh@chromium.org, May 11 2017

Cc: f...@chromium.org
are the metrics team able to pick this work up

Comment 5 by f...@chromium.org, May 27 2017 

Re #4: I don't have enough background to understand what this bug is about. What's needed here?

Comment 6 by manzagop@chromium.org, Jun 5 2017 

Context is in go/chrome-rdv (which really should be external)
Project Member

Comment 7 by sheriffbot@chromium.org, Jun 6 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
►

Sign in to add a comment