New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 591694 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
NOT IN USE
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Print preview appear weird in www.google.pl.

Reported by lpa...@etouch.net, Mar 3 2016

Issue description

Chrome Version: 50.0.2661.11 (Official Build) d99fa8d200178bce07b02a15d79512e7236088ee-refs/branch-heads/2661@{#51} 32/64-bit.
OS: All (Win 7 Aero-Enabled).
Test URL: https://www.google.pl/intl/pl/chrome/business/browser/

Steps:
1. Launch chrome and navigate to above url.
2. Give print command on the page (Ctrl+P) and observe.

Actual: Print preview appear weird (Unnecessary dropdown menu is seen in the print preview)

Expected: Print preview should be proper.

This is a regression issue broken in M-49.

Manual regression range:
Good Build: 49.0.2569.0
Bad build : 49.0.2571.0

Narrow Bisect: 
https://chromium.googlesource.com/chromium/src/+log/30d7af01a3ce9006f8b8e21ee1e441bee2b1163a..a293493a93e9718f1a1f40208cca610512d0962d?pretty=fuller&n=100

Suspecting: r360798 ?
 

Comment 1 by msten...@opera.com, Mar 3 2016

Yes, caused by r360798.

Comment 2 by msten...@opera.com, Mar 3 2016

tc.html
565 bytes View Download

Comment 3 by msten...@opera.com, Sep 13 2016

See also  bug 646313 .

Comment 4 by msten...@opera.com, Sep 22 2016

Cc: msten...@opera.com
 Issue 646313  has been merged into this issue.
Project Member

Comment 5 by bugdroid1@chromium.org, Sep 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/9c39d45041f1441a7e279fe32160df3db02b2213

commit 9c39d45041f1441a7e279fe32160df3db02b2213
Author: mstensho <mstensho@opera.com>
Date: Thu Sep 22 15:40:14 2016

Content that starts before the first fragmentainer should stay where it is.

It should not undergo pagination, but rather remain in the underflow area of
the first fragmentainer. There's no reason to pull everything into the content
area of the first fragmentainer.

BUG= 591694 

Review-Url: https://codereview.chromium.org/2360253002
Cr-Commit-Position: refs/heads/master@{#420353}

[add] https://crrev.com/9c39d45041f1441a7e279fe32160df3db02b2213/third_party/WebKit/LayoutTests/fragmentation/content-preceding-first-fragmentainer.html
[modify] https://crrev.com/9c39d45041f1441a7e279fe32160df3db02b2213/third_party/WebKit/Source/core/layout/LayoutBlockFlow.cpp

Comment 6 by msten...@opera.com, Sep 22 2016

Status: Fixed (was: Assigned)

Sign in to add a comment