Revert of [Prerender] Restore request priorities when swapped in

Revert of [Prerender] Restore request priorities when swapped in (patchset #1 id:1 of https://codereview.chromium.org/2832473002/ )

Reason for revert:
Caused compile failures on Mac and Windows Beta official desktop continuous waterfall.

https://bugs.chromium.org/p/chromium/issues/detail?id=713223

Original issue's description:
> [Prerender] Restore request priorities when swapped in
> 
> Requests from prerendered contents have a IDLE priority, in order not to slow
> down visible pages.
> However, when the prerendered contents become visible, the request priorities
> were not reset back to their correct values, leading to bad prerendering
> performance.
> 
> In this CL, the priority management for prerender requests is moved to the
> PrerenderResourceThrottle/PrerendereContents.
> The original priorities are stored in the throttle, and restored when the
> prerender contents swaps in.
> A new public function is added to ResourceDispatcherHost to update a request
> priority, and its implementation reuses the existing code that updates the image
> priorities.
> 
> The prerender contents keeps a list of all the network resources that were
> started while the prerender is hidden. If this proves to be too large, pruning
> the list when responses are received should be doable.
> 
> BUG=705955
> 
> Review-Url: https://codereview.chromium.org/2807163002
> Cr-Commit-Position: refs/heads/master@{#464728}
> (cherry picked from commit d3bc6148c7f0d2695ec2ca74652d996e2c4f5a6e)
> 
> Review-Url: https://codereview.chromium.org/2832473002 .
> Cr-Commit-Position: refs/branch-heads/3071@{#48}
> Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
> Committed: https://chromium.googlesource.com/chromium/src/+/d4b0c9f58ec981f98342cb8438da1a69bb489a06

TBR=droger@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=705955
Review-Url: https://codereview.chromium.org/2833553002
Cr-Commit-Position: refs/branch-heads/3071@{#58}
Cr-Branched-From: a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
Committed: https://chromium.googlesource.com/chromium/src/+/e8cd36ed2928f6e667386a687068e6a1de4124fe

[ojan, 2017-04-19 18:22:19]

The CQ bit was checked by ojan@chromium.org

[ojan, 2017-04-19 18:22:20]

Created Revert of [Prerender] Restore request priorities when swapped in

[commit-bot: I haz the power, 2017-04-19 18:22:50]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-19 18:23:32]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492626139844080, "parent_rev":
"a3ba22889b3f2565f6e430eca4a827e0e52e0301", "commit_rev":
"e8cd36ed2928f6e667386a687068e6a1de4124fe"}

[commit-bot: I haz the power, 2017-04-19 18:23:45]

Description was changed from

==========
Revert of [Prerender] Restore request priorities when swapped in (patchset #1
id:1 of https://codereview.chromium.org/2832473002/ )

Reason for revert:
Caused compile failures on Mac and Windows Beta official desktop continuous
waterfall.

https://bugs.chromium.org/p/chromium/issues/detail?id=713223

Original issue's description:
> [Prerender] Restore request priorities when swapped in
> 
> Requests from prerendered contents have a IDLE priority, in order not to slow
> down visible pages.
> However, when the prerendered contents become visible, the request priorities
> were not reset back to their correct values, leading to bad prerendering
> performance.
> 
> In this CL, the priority management for prerender requests is moved to the
> PrerenderResourceThrottle/PrerendereContents.
> The original priorities are stored in the throttle, and restored when the
> prerender contents swaps in.
> A new public function is added to ResourceDispatcherHost to update a request
> priority, and its implementation reuses the existing code that updates the
image
> priorities.
> 
> The prerender contents keeps a list of all the network resources that were
> started while the prerender is hidden. If this proves to be too large, pruning
> the list when responses are received should be doable.
> 
> BUG=705955
> 
> Review-Url: https://codereview.chromium.org/2807163002
> Cr-Commit-Position: refs/heads/master@{#464728}
> (cherry picked from commit d3bc6148c7f0d2695ec2ca74652d996e2c4f5a6e)
> 
> Review-Url: https://codereview.chromium.org/2832473002 .
> Cr-Commit-Position: refs/branch-heads/3071@{#48}
> Cr-Branched-From:
a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
> Committed:
https://chromium.googlesource.com/chromium/src/+/d4b0c9f58ec981f98342cb8438da...

TBR=droger@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=705955
==========

to

==========
Revert of [Prerender] Restore request priorities when swapped in (patchset #1
id:1 of https://codereview.chromium.org/2832473002/ )

Reason for revert:
Caused compile failures on Mac and Windows Beta official desktop continuous
waterfall.

https://bugs.chromium.org/p/chromium/issues/detail?id=713223

Original issue's description:
> [Prerender] Restore request priorities when swapped in
> 
> Requests from prerendered contents have a IDLE priority, in order not to slow
> down visible pages.
> However, when the prerendered contents become visible, the request priorities
> were not reset back to their correct values, leading to bad prerendering
> performance.
> 
> In this CL, the priority management for prerender requests is moved to the
> PrerenderResourceThrottle/PrerendereContents.
> The original priorities are stored in the throttle, and restored when the
> prerender contents swaps in.
> A new public function is added to ResourceDispatcherHost to update a request
> priority, and its implementation reuses the existing code that updates the
image
> priorities.
> 
> The prerender contents keeps a list of all the network resources that were
> started while the prerender is hidden. If this proves to be too large, pruning
> the list when responses are received should be doable.
> 
> BUG=705955
> 
> Review-Url: https://codereview.chromium.org/2807163002
> Cr-Commit-Position: refs/heads/master@{#464728}
> (cherry picked from commit d3bc6148c7f0d2695ec2ca74652d996e2c4f5a6e)
> 
> Review-Url: https://codereview.chromium.org/2832473002 .
> Cr-Commit-Position: refs/branch-heads/3071@{#48}
> Cr-Branched-From:
a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
> Committed:
https://chromium.googlesource.com/chromium/src/+/d4b0c9f58ec981f98342cb8438da...

TBR=droger@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=705955

Review-Url: https://codereview.chromium.org/2833553002
Cr-Commit-Position: refs/branch-heads/3071@{#58}
Cr-Branched-From:
a106f0abbf69dad349d4aaf4bcc4f5d376dd2377-refs/heads/master@{#464641}
Committed:
https://chromium.googlesource.com/chromium/src/+/e8cd36ed2928f6e667386a687068...
==========

[commit-bot: I haz the power, 2017-04-19 18:23:46]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/e8cd36ed2928f6e667386a687068...