diff options
| author | japhet <japhet@chromium.org> | 2016-03-23 11:51:00 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-03-23 18:52:44 +0000 |
| commit | 243c3522db99d0a7d7174fc91ae0f0591eedd062 (patch) | |
| tree | c4a6909e523e21d265b22948af4f8915b133b6fd /mojo | |
| parent | c1145be2aceccdd611023110471355caaabc46ed (diff) | |
| download | chromium_src-243c3522db99d0a7d7174fc91ae0f0591eedd062.zip chromium_src-243c3522db99d0a7d7174fc91ae0f0591eedd062.tar.gz chromium_src-243c3522db99d0a7d7174fc91ae0f0591eedd062.tar.bz2 | |
Simplify parsing/loading state, attempt #2
It seemed strange that DocumentLoader::stopLoading() both stops
fetching via ResourceFetcher::stopFetching() and reports a
cancellation via DocumentLoader::cancelMainResourceLoad().
Turns out, a lot of legacy logic is only needed to make that
cancelMainResourceLoad() call work correctly. Replace it with
a smaller, more container hack in FrameLoader::stopAllLoaders.
BUG=
Review URL: https://codereview.chromium.org/1823863002
Cr-Commit-Position: refs/heads/master@{#382892}
Diffstat (limited to 'mojo')
0 files changed, 0 insertions, 0 deletions