Revert 47347 - (Original patch reviewed at http://codereview.chromium.org/206...

Revert 47347 - (Original patch reviewed at http://codereview.chromium.org/2067003 )

Track "display" and "run" separately for mixed content, and make the latter downgrade the SSL state to "authentication broken".

Make the "display" state only affect the current tab (not the entire host).

Fix an SSL browser test by supplying the appropriate SiteInstance*.

Move a test from "disabled" to "flaky" since it at least passes for me.

Make the SSLManager header and .cc files put functions in the same order, and make that order somewhat saner.


Falied TestGoodFrameNavigation on Mac 10.5 browser tests

among other things:
/b/slave/chromium-rel-mac-builder/build/src/chrome/browser/ssl/ssl_browser_tests.cc:43: Failure
Value of: entry->ssl().displayed_mixed_content()
  Actual: false
Expected: displayed_mixed_content
Which is: true


BUG=15072, 18626, 40932, 42758
TEST=Covered by browser tests
Review URL: http://codereview.chromium.org/2063008

TBR=pkasting@chromium.org

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=47357

[Peter Kasting, 2010-05-15 20:38:03]

I don't understand why a test that's marked FLAKY is causing the bot to turn
red.

[rvargas (doing something else), 2010-05-17 16:42:43]

I don't know the exact mechanics to turn a particular bot red with a test
marked flaky, but the test started to fail consistently (aka, not flaky
anymore) and the failure looks like a consequence of this cl.

On Sat, May 15, 2010 at 1:38 PM, <pkasting@chromium.org> wrote:

> I don't understand why a test that's marked FLAKY is causing the bot to
> turn
> red.
>
>
> http://codereview.chromium.org/2095006/show
>

[Peter Kasting, 2010-05-17 17:25:19]

On Mon, May 17, 2010 at 9:42 AM, Ricardo Vargas <rvargas@chromium.org>wrote:

> I don't know the exact mechanics to turn a particular bot red with a test
> marked flaky, but the test started to fail consistently (aka, not flaky
> anymore) and the failure looks like a consequence of this cl.


The only thing that affected this is that I changed the test from DISABLED
to FLAKY, which caused it to be run at all.  On the Mac, this test times
out, and FLAKY does not cover timeouts.  Therefore the only way to go is to
check in without un-disabling the test, and then figure out how to make it
work on the Mac.

I will re-land the patch leaving that test DISABLED for Mac for now.


> http://codereview.chromium.org/2095006/show
>>
>
>