New issue
Advanced search Search tips

Issue 816927 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

SetBrowserClientForTesting() calls might not get cleaned up in case of ASSERT failures

Project Member Reported by est...@chromium.org, Feb 27 2018

Issue description

SSLUIWorkerFetchTest.MAYBE_MixedContentSettings calls content::SetBrowserClientForTesting() at the beginning and end. It's unclear if the client will get reset in the case of an ASSERT failure, when the test bails out early. As a matter of best practice, it's probably best to do it on TearDown() instead.
 

Sign in to add a comment