Revert of Introduce an intra-priority level sorting value - Chromium Side

Revert of Introduce an intra-priority level sorting value - Chromium Side (https://codereview.chromium.org/146333004/)

Reason for revert:
Broke a layout test, http/tests/loading/promote-img-in-viewport-priority.html

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20Blink&tests=http%2Ftests%2Floading%2Fpromote-img-in-viewport-priority.html

Original issue's description:
> This CL adds an intra-priority level sorting value for finer grained control of resource loading. The blink side of this patch sorts visible images by estimated on screen real-estate, preferring to download images with more visual impact first.  Ie. On a page with a large banner, and dozens of small icons, the large banner will most likely be scheduled ahead of the others. 
> 
> In the future, we can also use this to experiment with other signals, ie. prioritize by distance to viewport.
> 
> This needs https://codereview.chromium.org/153983004/ to land first.
> 
> In our tests, this was a nice win on speed-index for desktop, with a gain of about ~2-3%.
> 
> BUG=
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260665

TBR=simonjam@chromium.org,darin@chromium.org,cevans@chromium.org,simonhatch@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=260772

[tkent, 2014-04-01 04:09:36]

Created Revert of Introduce an intra-priority level sorting value - Chromium
Side

[commit-bot: I haz the power, 2014-04-01 04:10:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tkent@chromium.org/220553002/1

[commit-bot: I haz the power, 2014-04-01 04:11:02]

Change committed as 260772

[shatch, 2014-04-01 17:58:29]

On 2014/04/01 04:11:02, I haz the power (commit-bot) wrote:
> Change committed as 260772

So think I need to land a change to the
http/tests/loading/promote-img-in-viewport-priority.html to account for the new
output. Looks like the proper way to do this is to:

1. Make the change in blink.
2. Modify src/webkit/tools/layout_tests/test_expecations.txt to expect the
failure until the next blink roll.

Is that right?

[tkent, 2014-04-02 00:13:21]

On 2014/04/01 17:58:29, shatch wrote:
> On 2014/04/01 04:11:02, I haz the power (commit-bot) wrote:
> > Change committed as 260772
> 
> So think I need to land a change to the
> http/tests/loading/promote-img-in-viewport-priority.html to account for the
new
> output. Looks like the proper way to do this is to:
> 
> 1. Make the change in blink.
> 2. Modify src/webkit/tools/layout_tests/test_expecations.txt to expect the
> failure until the next blink roll.
> 
> Is that right?

In this procedure, Blink bots will fail between 1 and 2.

I recommend:
  1. Update promote-img-in-viewport-priority.html and
LayoutTests/TestExpectation so that the test failure is expected.
  2. Wait for a Blink roll.
  3. Land the Chromium change again
  4. Revert LayoutTests/TestExpectation

[shatch, 2014-04-02 17:53:02]

On 2014/04/02 00:13:21, tkent wrote:
> On 2014/04/01 17:58:29, shatch wrote:
> > On 2014/04/01 04:11:02, I haz the power (commit-bot) wrote:
> > > Change committed as 260772
> > 
> > So think I need to land a change to the
> > http/tests/loading/promote-img-in-viewport-priority.html to account for the
> new
> > output. Looks like the proper way to do this is to:
> > 
> > 1. Make the change in blink.
> > 2. Modify src/webkit/tools/layout_tests/test_expecations.txt to expect the
> > failure until the next blink roll.
> > 
> > Is that right?
> 
> In this procedure, Blink bots will fail between 1 and 2.
> 
> I recommend:
>   1. Update promote-img-in-viewport-priority.html and
> LayoutTests/TestExpectation so that the test failure is expected.
>   2. Wait for a Blink roll.
>   3. Land the Chromium change again
>   4. Revert LayoutTests/TestExpectation

Awesome, thanks for the clarification!