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

Issue 700919 link

Starred by 7 users

Issue metadata

Status: Fixed
Owner:
NOT IN USE
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 591099



Sign in to add a comment

Printing page breaks not correct with floated container

Reported by andrewdi...@mso.net, Mar 13 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1) Create an HTML page with the following code:

<html>
<body>
<div style="float:left;">
<div style="page-break-after:always;">T1</div>
<div style="page-break-after:always;">T2</div>
<div style="page-break-after:always;">T3</div>
<div style="page-break-after:always;">T4</div>
</div>
</body>
</html>

2) Open the HTML page in Chrome

3) Select to print the page and you will see in the print preview that the page breaks have been ignored.

4) If you remove the "float: left" from the container DIV, it will break it over 4 pages as expected.

Please note, the code shown in step 1 works as expected, e.g. breaking over 4 pages, in Firefox and Safari.

What is the expected behavior?
For it to respect the page breaks.

What went wrong?
It didn't respect the page breaks.

Did this work before? N/A 

Chrome version: 56.0.2924.87  Channel: n/a
OS Version: OS X 10.12.3
Flash Version: 

There was previously a ticket for this  issue #118627 , which was closed as "Won't Fix", with a comment saying it was now working.
 
Components: Internals>Printing Blink>Layout
Status: Untriaged (was: Unconfirmed)

Comment 2 by e...@chromium.org, Mar 14 2017

Blockedon: 591099
Labels: -Type-Bug Type-Feature
I don't think we support fragmenting floats. This is likely something that we won't fix until LayoutNG as it would be very hard in our current architecture.

Comment 3 by e...@chromium.org, Mar 14 2017

Status: Ava (was: Untriaged)

Comment 4 by e...@chromium.org, Mar 14 2017

Labels: -Pri-2 Pri-3
Status: Available (was: ava)

Comment 5 by andrewdi...@mso.net, Mar 17 2017

Is there a timeframe for the implementation of LayoutNG?

Comment 6 by msten...@opera.com, Apr 24 2017

Cc: msten...@opera.com
Labels: -OS-Mac
We do support fragmenting floats, but we ignore any forced breaks inside them - i.e. only unforced breaks are supported. I'm not sure if there's a good reason for prohibiting forced breaks inside floats. We already do support parallel flows anyway.

Comment 7 by msten...@opera.com, Apr 24 2017

Owner: msten...@opera.com
Status: Assigned (was: Available)
I find no reason to prohibit forced breaks inside floats, so I'll just fix it.

Comment 9 by msten...@opera.com, Apr 25 2017

Status: Fixed (was: Assigned)
Cc: thestig@chromium.org
 Issue 735012  has been merged into this issue.

Sign in to add a comment