Revert of Fragment blocks with non-visible overflow as normally when printing.

Revert of Fragment blocks with non-visible overflow as normally when printing. (patchset #1 id:1 of https://codereview.chromium.org/2298193002/ )

Reason for revert:
Suspected cause of "virtual/threaded/fast/scroll-behavior/smooth-scroll/main-thread-scrolling-reason-correctness.html" failures in webkit_tests on "WebKit Linux (dbg)" bot.

example: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg%29/builds/9099

Original issue's description:
> Fragment blocks with non-visible overflow as normally when printing.
>
> Splitting scrollbars into multiple fragmentainers is only problematic in
> interactive media. We don't need to impose any such pagination restrictions
> when printing, since printing is non-interactive,
>
> BUG=641983
>
> Committed: https://crrev.com/53d4d7aff8e25eae2ece5bbf5a53eec940871fa8
> Cr-Commit-Position: refs/heads/master@{#415645}

TBR=eae@chromium.org,mstensho@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=641983
Committed: https://crrev.com/0928918d8e570a7367a571d158a34933077e7022
Cr-Commit-Position: refs/heads/master@{#415712}

[paulmeyer, 2016-08-31 19:09:56]

The CQ bit was checked by paulmeyer@chromium.org

[paulmeyer, 2016-08-31 19:09:56]

Created Revert of Fragment blocks with non-visible overflow as normally when
printing.

[commit-bot: I haz the power, 2016-08-31 19:10:23]

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-08-31 19:11:15]

Description was changed from

==========
Revert of Fragment blocks with non-visible overflow as normally when printing.
(patchset #1 id:1 of https://codereview.chromium.org/2298193002/ )

Reason for revert:
Suspected cause of
"virtual/threaded/fast/scroll-behavior/smooth-scroll/main-thread-scrolling-reason-correctness.html"
failures in webkit_tests on "WebKit Linux (dbg)" bot.

example:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg...

Original issue's description:
> Fragment blocks with non-visible overflow as normally when printing.
> 
> Splitting scrollbars into multiple fragmentainers is only problematic in
> interactive media. We don't need to impose any such pagination restrictions
> when printing, since printing is non-interactive,
> 
> BUG=641983
> 
> Committed: https://crrev.com/53d4d7aff8e25eae2ece5bbf5a53eec940871fa8
> Cr-Commit-Position: refs/heads/master@{#415645}

TBR=eae@chromium.org,mstensho@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=641983
==========

to

==========
Revert of Fragment blocks with non-visible overflow as normally when printing.
(patchset #1 id:1 of https://codereview.chromium.org/2298193002/ )

Reason for revert:
Suspected cause of
"virtual/threaded/fast/scroll-behavior/smooth-scroll/main-thread-scrolling-reason-correctness.html"
failures in webkit_tests on "WebKit Linux (dbg)" bot.

example:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg...

Original issue's description:
> Fragment blocks with non-visible overflow as normally when printing.
> 
> Splitting scrollbars into multiple fragmentainers is only problematic in
> interactive media. We don't need to impose any such pagination restrictions
> when printing, since printing is non-interactive,
> 
> BUG=641983
> 
> Committed: https://crrev.com/53d4d7aff8e25eae2ece5bbf5a53eec940871fa8
> Cr-Commit-Position: refs/heads/master@{#415645}

TBR=eae@chromium.org,mstensho@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=641983
==========

[commit-bot: I haz the power, 2016-08-31 19:11:18]

Committed patchset #1 (id:1)

[eae, 2016-08-31 19:13:25]

LGTM

[commit-bot: I haz the power, 2016-08-31 19:14:27]

Description was changed from

==========
Revert of Fragment blocks with non-visible overflow as normally when printing.
(patchset #1 id:1 of https://codereview.chromium.org/2298193002/ )

Reason for revert:
Suspected cause of
"virtual/threaded/fast/scroll-behavior/smooth-scroll/main-thread-scrolling-reason-correctness.html"
failures in webkit_tests on "WebKit Linux (dbg)" bot.

example:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg...

Original issue's description:
> Fragment blocks with non-visible overflow as normally when printing.
> 
> Splitting scrollbars into multiple fragmentainers is only problematic in
> interactive media. We don't need to impose any such pagination restrictions
> when printing, since printing is non-interactive,
> 
> BUG=641983
> 
> Committed: https://crrev.com/53d4d7aff8e25eae2ece5bbf5a53eec940871fa8
> Cr-Commit-Position: refs/heads/master@{#415645}

TBR=eae@chromium.org,mstensho@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=641983
==========

to

==========
Revert of Fragment blocks with non-visible overflow as normally when printing.
(patchset #1 id:1 of https://codereview.chromium.org/2298193002/ )

Reason for revert:
Suspected cause of
"virtual/threaded/fast/scroll-behavior/smooth-scroll/main-thread-scrolling-reason-correctness.html"
failures in webkit_tests on "WebKit Linux (dbg)" bot.

example:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20%28dbg...

Original issue's description:
> Fragment blocks with non-visible overflow as normally when printing.
>
> Splitting scrollbars into multiple fragmentainers is only problematic in
> interactive media. We don't need to impose any such pagination restrictions
> when printing, since printing is non-interactive,
>
> BUG=641983
>
> Committed: https://crrev.com/53d4d7aff8e25eae2ece5bbf5a53eec940871fa8
> Cr-Commit-Position: refs/heads/master@{#415645}

TBR=eae@chromium.org,mstensho@opera.com
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=641983

Committed: https://crrev.com/0928918d8e570a7367a571d158a34933077e7022
Cr-Commit-Position: refs/heads/master@{#415712}
==========

[commit-bot: I haz the power, 2016-08-31 19:14:28]

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

[mstensho (USE GERRIT), 2016-08-31 19:16:36]

I think you need to keep looking for the culprit. This one should be innocent.
:)

[mstensho (USE GERRIT), 2016-09-01 18:26:29]

I'd like to reland this unless we have good reasons to believe that reverting it
fixed something.

[paulmeyer, 2016-09-01 19:49:26]

On 2016/09/01 18:26:29, mstensho wrote:
> I'd like to reland this unless we have good reasons to believe that reverting
it
> fixed something.

Yeah, you're right, we're still seeing that failure.

[paulmeyer, 2016-09-01 19:49:55]

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

The reason for reverting is: The reverted CL seems not to have been the
problem..

[mstensho (USE GERRIT), 2016-09-01 19:51:40]

Thanks!