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

Issue 659343 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 660839
Owner:
Not on Chrome anymore
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression
M54



Sign in to add a comment

page-break-after:always / page_break_before:always no longer work

Reported by wrs...@gmail.com, Oct 25 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:
1. View index.html (fixed size pages) or index2.html (non-fixed size pages) in the Chrome Browser
2. Right click on screen and select Print
3. View page breaks being incorrectly inserted through text / after text in the print preview

What is the expected behavior?
the expected behavior is for each Div to print on a separate page.

What went wrong?
Each Div did not print on a separate page.

Did this work before? Yes 54.0.2840.59

Does this work in other browsers? Yes

Chrome version: 54.0.2840.71  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
 
index2.html
1.4 KB View Download
Page Break Print Test Output.pdf
29.6 KB Download
Page Break Print Test Output 2.pdf
28.7 KB Download
Labels: Needs-Feedback
The two attached test html files appear to be identical. Can you please check?

Comment 2 by wrs...@gmail.com, Oct 26 2016

Sorry about that.  The first index.html file was supposed to have formatting to dimension the Divs to the size of a 8.5" x 11" portrait oriented sheet of paper.  Attached is the correct example.  In the second example, I removed the dimension formatting.  I included the two examples to show that the page-break-after does break the page, but in the wrong place, whether the html is formatted for pages or not.  
index.html
1.4 KB View Download

Comment 3 by wrs...@gmail.com, Oct 26 2016

I also tested the issue on Linux Fedora 24 with the same version of Chrome Stable, 54.0.2840.71, and got the same results, so the issue appears to not be operating system specific.

Comment 4 by wrs...@gmail.com, Oct 26 2016

The problem I was experiencing was due to the following CSS:
@page {
    size: portrait;
}

Removing that code from the example resolved the problem.  Also changing the code to 

@page {
    size: letter portrait;
}

or 

@page {
    size: auto portrait;
}

works as well.
Users reported the same issue for a web application we support that uses Chrome's print view.  Due to the sensitive nature of the material I can't post examples.  However, I can reproduce behavior if needed.     


What is the expected behavior?
the expected behavior is for each Div to print on a separate page.

What went wrong?
Each Div did not print on a separate page.

Did this work before? Yes 54.0.2840.59

Does this work in other browsers? 

Yes.  Microsoft Edge works.  

Microsoft Edge 25.10586.0.0
Microsft EdgeHTML 13.10586
 
My PC:
Chrome Version. Version 54.0.2840.71 m (64-bit)
Windows 10 Pro Version 1511 OS. 10586.633

Comment 6 by phistuck@gmail.com, Oct 27 2016

#5 - unrelated, but your Windows is not up to date, EdgeHTML 14 is the current stable release.
Project Member

Comment 7 by sheriffbot@chromium.org, Nov 4 2016

Labels: -Needs-Feedback Needs-Review
Owner: mikelawther@chromium.org
Thank you for providing more feedback. Adding requester "mikelawther@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -Blink>CSS Internals>Printing
Labels: -Type-Bug -Needs-Review Needs-Bisect Type-Bug-Regression
Status: Available (was: Unconfirmed)
Able to repro regression, seeing text split across pages in index2.html print preview on Windows Chrome 55. Requesting bisect.
Owner: ----
Status: Untriaged (was: Available)
Thanks Alan, removing myself as owner now while test team bisects this.
Cc: jmukthavaram@chromium.org
Labels: -Pri-2 -Needs-Bisect hasbisect-per-revision M54 Pri-1
Owner: nainar@chromium.org
Able to reproduce this issue on windows 7 & 10 with Chrome stable version-54.0.2840.87 and Canary-56.0.2912.0.

Manual Bisect:
--------------
Bad Build—54.0.2821.0 --Revision--410228

Good Build—54.0.2820.0 --Revision--409955

Bisect Tool Info:
-----------------
CL-

https://chromium.googlesource.com/chromium/src/+log/a9094bdb2cda679e8bf3a5b43b27c12efa975d3c..fc1140de1b4563d3d890512e4a4f5f6481dddd0f

Possible suspect:

https://chromium.googlesource.com/chromium/src/+/a7760a764855fb5678f7e5e88e11b834416ffbb7


nainar@ assigning to you, as you were listed as one of the reviewers for this CL.

Kindly take a look and please help us to reassign this issue to a right owner if not with respect to this change.

Thanks.!
Status: Assigned (was: Untriaged)
Mergedinto: 660839
Status: Duplicate (was: Assigned)

Sign in to add a comment