Reland of -enable GPU Rasterization for content with any author defined viewport.

Reland of -enable GPU Rasterization for content with any author defined viewport. (patchset #1 id:1 of https://codereview.chromium.org/2156553002/ )

Reason for revert:
Reverting change now that we have collected data from telemetry.

Original issue's description:
> Revert of Re-enable GPU Rasterization for content with any author defined viewport. (patchset #2 id:20001 of https://codereview.chromium.org/2097413003/ )
>
> Reason for revert:
> This has caused an unexpectedly large regression in overall PSS (about 5MB, graph here: https://chromeperf.appspot.com/report?sid=0b072725c25637efb0d3a44383da1e24e42bbb3740a00505e4040af2173423b0&start_rev=402061&end_rev=402790).
> The owners are both OOO and this is blocking Android release. This has already been reverted in the release branch but our infrastructure cannot gather data from the branch to confirm that the revert has had the intended result.
>
> This revert will allow us to confirm that this CL was the cause of the regression. Once confirmed (or otherwise) via telemetry dashboards this revert will be re-reverted.
>
> Original issue's description:
> > Re-enable GPU Rasterization for content with any author defined viewport.
> >
> > BUG=591179
> >
> > Committed: https://crrev.com/a017b667a53b3ee5f8bc630be98c37ebf53a2339
> > Cr-Commit-Position: refs/heads/master@{#402702}
>
> TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=591179
>
> Committed: https://crrev.com/10a77702aa0490dfaaa6e354151b24b738474fb4
> Cr-Commit-Position: refs/heads/master@{#405750}

TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org,primiano@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=591179
Committed: https://crrev.com/5f19720ded2369857bee408ab48e11e7b5d28f7b
Cr-Commit-Position: refs/heads/master@{#405974}

[picksi1, 2016-07-18 09:51:40]

The CQ bit was checked by picksi@chromium.org

[picksi1, 2016-07-18 09:51:41]

Created Reland of -enable GPU Rasterization for content with any author defined
viewport.

[commit-bot: I haz the power, 2016-07-18 09:51:47]

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, 2016-07-18 09:51:48]

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

[commit-bot: I haz the power, 2016-07-18 09:51:48]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Primiano Tucci (use gerrit), 2016-07-18 09:52:59]

lgtm

[picksi1, 2016-07-18 09:53:23]

The CQ bit was checked by picksi@chromium.org

[commit-bot: I haz the power, 2016-07-18 09:53:42]

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, 2016-07-18 11:04:48]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-18 11:04:50]

CQ bit was unchecked.

[commit-bot: I haz the power, 2016-07-18 11:06:59]

Description was changed from

==========
Reland of -enable GPU Rasterization for content with any author defined
viewport. (patchset #1 id:1 of https://codereview.chromium.org/2156553002/ )

Reason for revert:
Reverting change now that we have collected data from telemetry.

Original issue's description:
> Revert of Re-enable GPU Rasterization for content with any author defined
viewport. (patchset #2 id:20001 of https://codereview.chromium.org/2097413003/ )
> 
> Reason for revert:
> This has caused an unexpectedly large regression in overall PSS (about 5MB,
graph here:
https://chromeperf.appspot.com/report?sid=0b072725c25637efb0d3a44383da1e24e42...).
> The owners are both OOO and this is blocking Android release. This has already
been reverted in the release branch but our infrastructure cannot gather data
from the branch to confirm that the revert has had the intended result.
> 
> This revert will allow us to confirm that this CL was the cause of the
regression. Once confirmed (or otherwise) via telemetry dashboards this revert
will be re-reverted.
> 
> Original issue's description:
> > Re-enable GPU Rasterization for content with any author defined viewport.
> >
> > BUG=591179
> >
> > Committed: https://crrev.com/a017b667a53b3ee5f8bc630be98c37ebf53a2339
> > Cr-Commit-Position: refs/heads/master@{#402702}
> 
> TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=591179
> 
> Committed: https://crrev.com/10a77702aa0490dfaaa6e354151b24b738474fb4
> Cr-Commit-Position: refs/heads/master@{#405750}

TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org,primiano@ch...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=591179
==========

to

==========
Reland of -enable GPU Rasterization for content with any author defined
viewport. (patchset #1 id:1 of https://codereview.chromium.org/2156553002/ )

Reason for revert:
Reverting change now that we have collected data from telemetry.

Original issue's description:
> Revert of Re-enable GPU Rasterization for content with any author defined
viewport. (patchset #2 id:20001 of https://codereview.chromium.org/2097413003/ )
>
> Reason for revert:
> This has caused an unexpectedly large regression in overall PSS (about 5MB,
graph here:
https://chromeperf.appspot.com/report?sid=0b072725c25637efb0d3a44383da1e24e42...).
> The owners are both OOO and this is blocking Android release. This has already
been reverted in the release branch but our infrastructure cannot gather data
from the branch to confirm that the revert has had the intended result.
>
> This revert will allow us to confirm that this CL was the cause of the
regression. Once confirmed (or otherwise) via telemetry dashboards this revert
will be re-reverted.
>
> Original issue's description:
> > Re-enable GPU Rasterization for content with any author defined viewport.
> >
> > BUG=591179
> >
> > Committed: https://crrev.com/a017b667a53b3ee5f8bc630be98c37ebf53a2339
> > Cr-Commit-Position: refs/heads/master@{#402702}
>
> TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org
> # Not skipping CQ checks because original CL landed more than 1 days ago.
> BUG=591179
>
> Committed: https://crrev.com/10a77702aa0490dfaaa6e354151b24b738474fb4
> Cr-Commit-Position: refs/heads/master@{#405750}

TBR=aelias@chromium.org,chrishtr@chromium.org,vmiura@chromium.org,primiano@ch...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=591179

Committed: https://crrev.com/5f19720ded2369857bee408ab48e11e7b5d28f7b
Cr-Commit-Position: refs/heads/master@{#405974}
==========

[commit-bot: I haz the power, 2016-07-18 11:07:01]

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

[picksi1, 2016-07-18 14:08:31]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2155193002/ by picksi@chromium.org.

The reason for reverting is: Relanding this has potentially caused a layout test
to fail
(https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg...).
The build sheriff has asked me to revert it.

Adding aelias & vmiura so they can do a more refined revert on their return from
vacation..