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

Issue 671717 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
█ nick@chromium.org
rdevlin....@chromium.org
█ nasko@chromium.org
wfh@chromium.org
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

extension_browsertests should know about --isolate-extensions

Project Member Reported by lukasza@chromium.org, Dec 6 2016 
We should move the code that handles --isolate-extensions switch from the //chrome layer into //extensions layer.  This will enable running of extension_browsertests with --isolate-extensions switch (rather than with --site-per-process).  This will also result in better layering (--isolate-extensions switch is an extension thing and should therefore live in the //extensions layer, not in the //chrome layer).
Project Member

Comment 1 by sheriffbot@chromium.org, Dec 11 2017

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

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

Comment 2 by nasko@chromium.org, Dec 16 2017

Status: WontFix (was: Untriaged)
Given that --isolate-extensions is now the default behavior and cannot be disabled, is this bug still relevant? It doesn't seem so to me, so we can close it. Reopen it if I've missed something.
►

Sign in to add a comment