Revert of Move 'frame-src' CSP checks into FrameFetchContext.

Revert of Move 'frame-src' CSP checks into FrameFetchContext. (patchset #5 id:100001 of https://codereview.chromium.org/2022083002/ )

Reason for revert:
Speculative revert for breaking Dr. Memory:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%20Browser%20%28DrMemory%20full%29%20%284%29?numbuilds=200

First breaking build:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%20Browser%20%28DrMemory%20full%29%20%284%29/builds/8028

Original issue's description:
> Move 'frame-src' CSP checks into FrameFetchContext.
>
> Currently, we're doing 'frame-src' checks inside 'FrameLoader', which
> ends up being too early in the navigation cycle to handle the results
> of 'upgrade-insecure-requests'. Happily, we've refactored enough of the
> loading code in the last ~3 years that we can pretty easily move this
> check into 'FrameFetchContext::canRequest' alongside the rest of CSP.
>
> BUG=615910
>
> Committed: https://crrev.com/3f3e725e6479c711e5e13e59e8d011ee89992119
> Cr-Commit-Position: refs/heads/master@{#398685}

TBR=jialiul@chromium.org,alexmos@chromium.org,creis@chromium.org,dcheng@chromium.org,japhet@chromium.org,jochen@chromium.org,lukasza@chromium.org,nasko@chromium.org,nparker@chromium.org,yoav@yoav.ws,mkwst@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615910
Committed: https://crrev.com/13632cf2d8145ab0785011bc4e1c7254914395fc
Cr-Commit-Position: refs/heads/master@{#399561}

[tommycli, 2016-06-13 18:13:03]

The CQ bit was checked by tommycli@chromium.org

[tommycli, 2016-06-13 18:13:04]

Created Revert of Move 'frame-src' CSP checks into FrameFetchContext.

[commit-bot: I haz the power, 2016-06-13 18:13:31]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2068443002/1

[commit-bot: I haz the power, 2016-06-13 18:16:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-13 18:16:30]

Try jobs failed on following builders:
  ios-simulator on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator/bui...)
  ios-simulator-gn on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-gn/...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_gn_rel on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_gn_r...)

[tommycli, 2016-06-13 19:32:24]

The CQ bit was checked by tommycli@chromium.org

[commit-bot: I haz the power, 2016-06-13 19:33:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2068443002/190001

[commit-bot: I haz the power, 2016-06-13 21:54:31]

Description was changed from

==========
Revert of Move 'frame-src' CSP checks into FrameFetchContext. (patchset #5
id:100001 of https://codereview.chromium.org/2022083002/ )

Reason for revert:
Speculative revert for breaking Dr. Memory:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

First breaking build:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

Original issue's description:
> Move 'frame-src' CSP checks into FrameFetchContext.
> 
> Currently, we're doing 'frame-src' checks inside 'FrameLoader', which
> ends up being too early in the navigation cycle to handle the results
> of 'upgrade-insecure-requests'. Happily, we've refactored enough of the
> loading code in the last ~3 years that we can pretty easily move this
> check into 'FrameFetchContext::canRequest' alongside the rest of CSP.
> 
> BUG=615910
> 
> Committed: https://crrev.com/3f3e725e6479c711e5e13e59e8d011ee89992119
> Cr-Commit-Position: refs/heads/master@{#398685}

TBR=jialiul@chromium.org,alexmos@chromium.org,creis@chromium.org,dcheng@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615910
==========

to

==========
Revert of Move 'frame-src' CSP checks into FrameFetchContext. (patchset #5
id:100001 of https://codereview.chromium.org/2022083002/ )

Reason for revert:
Speculative revert for breaking Dr. Memory:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

First breaking build:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

Original issue's description:
> Move 'frame-src' CSP checks into FrameFetchContext.
> 
> Currently, we're doing 'frame-src' checks inside 'FrameLoader', which
> ends up being too early in the navigation cycle to handle the results
> of 'upgrade-insecure-requests'. Happily, we've refactored enough of the
> loading code in the last ~3 years that we can pretty easily move this
> check into 'FrameFetchContext::canRequest' alongside the rest of CSP.
> 
> BUG=615910
> 
> Committed: https://crrev.com/3f3e725e6479c711e5e13e59e8d011ee89992119
> Cr-Commit-Position: refs/heads/master@{#398685}

TBR=jialiul@chromium.org,alexmos@chromium.org,creis@chromium.org,dcheng@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615910
==========

[commit-bot: I haz the power, 2016-06-13 21:54:32]

Committed patchset #2 (id:190001)

[commit-bot: I haz the power, 2016-06-13 21:56:06]

Description was changed from

==========
Revert of Move 'frame-src' CSP checks into FrameFetchContext. (patchset #5
id:100001 of https://codereview.chromium.org/2022083002/ )

Reason for revert:
Speculative revert for breaking Dr. Memory:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

First breaking build:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

Original issue's description:
> Move 'frame-src' CSP checks into FrameFetchContext.
> 
> Currently, we're doing 'frame-src' checks inside 'FrameLoader', which
> ends up being too early in the navigation cycle to handle the results
> of 'upgrade-insecure-requests'. Happily, we've refactored enough of the
> loading code in the last ~3 years that we can pretty easily move this
> check into 'FrameFetchContext::canRequest' alongside the rest of CSP.
> 
> BUG=615910
> 
> Committed: https://crrev.com/3f3e725e6479c711e5e13e59e8d011ee89992119
> Cr-Commit-Position: refs/heads/master@{#398685}

TBR=jialiul@chromium.org,alexmos@chromium.org,creis@chromium.org,dcheng@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615910
==========

to

==========
Revert of Move 'frame-src' CSP checks into FrameFetchContext. (patchset #5
id:100001 of https://codereview.chromium.org/2022083002/ )

Reason for revert:
Speculative revert for breaking Dr. Memory:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

First breaking build:

https://build.chromium.org/p/chromium.memory.fyi/builders/Windows%20Content%2...

Original issue's description:
> Move 'frame-src' CSP checks into FrameFetchContext.
>
> Currently, we're doing 'frame-src' checks inside 'FrameLoader', which
> ends up being too early in the navigation cycle to handle the results
> of 'upgrade-insecure-requests'. Happily, we've refactored enough of the
> loading code in the last ~3 years that we can pretty easily move this
> check into 'FrameFetchContext::canRequest' alongside the rest of CSP.
>
> BUG=615910
>
> Committed: https://crrev.com/3f3e725e6479c711e5e13e59e8d011ee89992119
> Cr-Commit-Position: refs/heads/master@{#398685}

TBR=jialiul@chromium.org,alexmos@chromium.org,creis@chromium.org,dcheng@chrom...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=615910

Committed: https://crrev.com/13632cf2d8145ab0785011bc4e1c7254914395fc
Cr-Commit-Position: refs/heads/master@{#399561}
==========

[commit-bot: I haz the power, 2016-06-13 21:56:07]

Patchset 2 (id:??) landed as
https://crrev.com/13632cf2d8145ab0785011bc4e1c7254914395fc
Cr-Commit-Position: refs/heads/master@{#399561}