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

Issue 732834 link

Starred by 10 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Printing cut off when using bootstrap grid

Reported by sethb...@gmail.com, Jun 13 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0

Steps to reproduce the problem:
Bootstrap is a set of CSS that has a grid of floats and when you try to print a list of them in chrome it cuts the list off in the print preview and when printed.

What is the expected behavior?
Use any other browser to see correct results.

What went wrong?
Printing cuts off

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110 (Official Build) (64-bit)  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 25.0 r0
 
test_chrome_bug.htm
14.7 KB View Download
Labels: Needs-Milestone
Cc: msrchandra@chromium.org
Components: UI>Browser>PrintPreview
Labels: -Needs-Milestone M-61 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Tested on Chrome Stable #59.0.3071.109, Canary #61.0.3137.0 on Windows 10 and able to reproduce the issue. Please find the screenshot for reference.
 
This is a non-regression issue and able to reproduce from M-30 #30.0.1599.0.Marking it as untriaged so that issue gets addressed.
 
Observations:
1. Able to reproduce this issue in Mac 10.12.5 and Ubuntu 14.04, whereas only 40% of the page is seen in the Print Preview.
2. Same behavior as Chrome is noticed on Internet Explorer 11, but in Firefox it seems to be good.
 
 
Thanks in advance.

Components: Blink>Layout
Labels: -M-61

Comment 4 by e...@chromium.org, Jun 30 2017

Cc: msten...@opera.com
Components: -UI>Browser>PrintPreview
Labels: -Pri-2 Pri-3
Status: Available (was: Untriaged)

Comment 5 by msten...@opera.com, Jul 17 2017

I don't find any screenshot, but here are a couple of observations:

First of all, when printing in Chrome, the "columns" are not laid out horizontally, but rather vertically, so each of them becomes a row inside the parent .row DIV. The CSS selectors that define the column (or rather floated) behavior lie inside a media query that requires the viewport or page box width to be at least 768px to have any effect. So the page box is not that wide when printing in Chrome, while it is in Firefox. Both browser-dependent and paper size dependent, I guess. This is not a bug. The style sheet needs to be fixed if you want columns even when the viewport/page box is narrower.

A real bug, on the other hand, is that we generate too few pages, so that the second half of the document (or more) is missing. I guess this is caused by some sort of incomplete re-layout when the "columns" go from being floated in screen mode to being non-floated in print mode.
reduction.html
13.4 KB View Download

Comment 6 by msten...@opera.com, Jul 17 2017

This bug occurs when a @media (min-width) query that used to match no longer matches, when printing. One would think that using "@media screen" instead would trigger the same bug, but no - then it works fine!
tc.html
1.1 KB View Download

Comment 7 by msten...@opera.com, Jul 17 2017

Cc: r...@opera.com

Comment 9 by msten...@opera.com, Sep 23 2017

Cc: shend@chromium.org
 Issue 764689  has been merged into this issue.

Comment 10 by msten...@opera.com, Oct 19 2017

Cc: sc00335...@techmahindra.com
 Issue 774853  has been merged into this issue.

Comment 11 by msten...@opera.com, Oct 19 2017

Labels: -Pri-3 Pri-2
Cc: -msten...@opera.com mstensho@chromium.org
Project Member

Comment 13 by sheriffbot@chromium.org, Dec 12

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Works fine in 72.0.3626.14

Sign in to add a comment