Lock page scale factor in tall-content-short-columns performance tests

Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content. We lock the page scale factor
to prevent this from happening and impacting performance.

The performance regression is caused by the sending of notifications
upon all changes to page scale factor whereas previously, these
notifications would not have been sent.

See https://codereview.chromium.org/1408393003/ where this behaviour
was changed.

BUG=555151
Committed: https://crrev.com/7030b20ca8a7a9868bf57341fbe55b28ad3ee6be
Cr-Commit-Position: refs/heads/master@{#360596}

[Kevin McNee - google account, 2015-11-18 18:02:03]

Description was changed from

==========
Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content.

BUG=555151
==========

to

==========
Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content. We lock the page scale factor
to prevent this from happening and impacting performance.

BUG=555151
==========

[Kevin McNee - google account, 2015-11-18 18:02:03]

mcnee@google.com changed reviewers:
+ paulmeyer@chromium.org, wjmaclean@chromium.org

[Kevin McNee - google account, 2015-11-18 18:15:53]

mcnee@google.com changed reviewers:
+ dsinclair@chromium.org

[Kevin McNee - google account, 2015-11-18 18:18:21]

dsinclair@: Hello. Could you take a look at this change?

[dsinclair, 2015-11-18 18:22:09]

dsinclair@chromium.org changed reviewers:
+ mstensho@opera.com

[dsinclair, 2015-11-18 18:22:09]

mstensho@ as the multi-col expert.

[Kevin McNee - google account, 2015-11-18 18:45:32]

Description was changed from

==========
Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content. We lock the page scale factor
to prevent this from happening and impacting performance.

BUG=555151
==========

to

==========
Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content. We lock the page scale factor
to prevent this from happening and impacting performance.
The performance regression is caused by the sending of notifications
upon all changes to page scale factor whereas previously, these notifications
would not have been sent.

BUG=555151
==========

[Kevin McNee - google account, 2015-11-18 18:52:02]

Description was changed from

==========
Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content. We lock the page scale factor
to prevent this from happening and impacting performance.
The performance regression is caused by the sending of notifications
upon all changes to page scale factor whereas previously, these notifications
would not have been sent.

BUG=555151
==========

to

==========
Lock page scale factor in tall-content-short-columns performance tests

During the tests, the changes to the content width cause the page scale
factor to be changed to fit the content. We lock the page scale factor
to prevent this from happening and impacting performance.

The performance regression is caused by the sending of notifications
upon all changes to page scale factor whereas previously, these
notifications would not have been sent.

See https://codereview.chromium.org/1408393003/ where this behaviour
was changed.

BUG=555151
==========

[mstensho (USE GERRIT), 2015-11-18 20:01:20]

lgtm

[Kevin McNee - google account, 2015-11-18 20:10:03]

The CQ bit was checked by mcnee@google.com

[commit-bot: I haz the power, 2015-11-18 20:10:13]

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

[commit-bot: I haz the power, 2015-11-18 21:07:40]

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

[commit-bot: I haz the power, 2015-11-18 21:07:40]

Try jobs failed on following builders:
  linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Kevin McNee - google account, 2015-11-18 21:35:26]

The CQ bit was checked by mcnee@google.com

[commit-bot: I haz the power, 2015-11-18 21:36:50]

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

[commit-bot: I haz the power, 2015-11-18 22:53:02]

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

[commit-bot: I haz the power, 2015-11-18 22:53:03]

Try jobs failed on following builders:
  linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Kevin McNee - google account, 2015-11-19 14:24:23]

The CQ bit was checked by mcnee@google.com

[commit-bot: I haz the power, 2015-11-19 14:24:32]

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

[commit-bot: I haz the power, 2015-11-19 16:18:02]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-19 16:18:45]

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