Add test to make sure HTMLPreloader requests are blocked on mixedContent requests.

Add test to make sure HTMLPreloader requests are blocked on mixedContent requests.

BUG=432771

[kouhei (in TOK), 2014-11-13 02:58:24]

kouhei@chromium.org changed reviewers:
+ japhet@chromium.org, mkwst@chromium.org, tyoshino@chromium.org

[tyoshino (SeeGerritForStatus), 2014-11-13 04:34:14]

Any idea why there're three console messages? Maybe the last one with a line
number info is for the actual loading. The other two are both for preloading?

[Mike West, 2014-11-13 08:41:44]

Hrm. It's not clear to me that we should be outputting console messages for
preloaded resources, as that process should be invisible to the page (and will
probably just confuse developers.

It's fine to land this patch as is, but please file a bug to remove the message
for preloaded resources and add it as a FIXME to the test's HTML file.

LGTM.

[tyoshino (SeeGerritForStatus), 2014-11-13 08:49:47]

On 2014/11/13 08:41:44, Mike West wrote:
> Hrm. It's not clear to me that we should be outputting console messages for
> preloaded resources, as that process should be invisible to the page (and will
> probably just confuse developers.
> 
> It's fine to land this patch as is, but please file a bug to remove the
message
> for preloaded resources and add it as a FIXME to the test's HTML file.
> 
> LGTM.

Hi Mike,

Kouhei figured out the reason why there're so many console errors, and we
discussed briefly if we should really print errors for both preloads and actual
loads and wanted your input :)

We agree that we shouldn't confuse developers. Let's remove messages for
preloads. Of course, anyway, we Chromium developers should make sure that
unexpected preloads don't happen even without the console errors. Hehe.

[kouhei (in TOK), 2014-11-17 03:41:57]

Included change in https://codereview.chromium.org/726563004/. Closing this
issue.