cc: Make corner cases of tile priority computation more simple.

cc: Make corner cases of tile priority computation more simple.

This changes tile priority computation so that max tile priority bin has
an effect only on priority bin but not on distance to visible. This
affects only tiles on layers which do not have valid tile priorities.

Committed: https://crrev.com/f89d183bfb64940c21e88ec802fd6c574c6a9564
Cr-Commit-Position: refs/heads/master@{#331086}

[USE eero AT chromium.org, 2015-05-21 12:31:20]

e.hakkinen@samsung.com changed reviewers:
+ enne@chromium.org, vmpstr@chromium.org

[USE eero AT chromium.org, 2015-05-21 12:31:21]

IMHO, as max tile priority bin does not have on effect on distance_to_visible
value of prioritized tiles within visible, skewport, soon border and eventually
rect, it should not have an effect within pending visible rect either. WDYT?

[vmpstr, 2015-05-21 17:24:49]

Sure this makes sense. Distance to visible is only used to figure out relative
ordering of tiles from different layers. So this would ensure that non valid
priority tile layers will have their soon to be visible tiles rasterized before
eventually tiles of other layers.

lgtm.

[USE eero AT chromium.org, 2015-05-22 08:26:40]

The CQ bit was checked by e.hakkinen@samsung.com

[commit-bot: I haz the power, 2015-05-22 08:27:00]

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

[commit-bot: I haz the power, 2015-05-22 09:29:31]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-22 09:30:20]

Patchset 1 (id:??) landed as
https://crrev.com/f89d183bfb64940c21e88ec802fd6c574c6a9564
Cr-Commit-Position: refs/heads/master@{#331086}