Bug 15546

Summary:

Incompatiblities between CSS columns and printing

Product:

WebKit

Reporter:

David Latapie <david>

Component:

Printing

Assignee:

Nobody <webkit-unassigned>

Status:

NEW

Severity:

Major

CC:

alexandre, bfulgham, chaffeqa, chrisjshull, claude.pache, dev, emacemac7, eric, ian, jkichline, jonas, matt.m.soria, mharen, mradosev, pfurbacher, seiz, simon.fraser, zalan

Priority:

Keywords:

InRadar

Version:

523.x (Safari 3)

Hardware:

Mac (Intel)

OS:

OS X 10.4

Attachments:

Description	Flags
Simple test. Two pages of lipsum to also test where the columns reset (end of doc or end of page)	none

David Latapie

Reported 2007-10-17 20:19:37 PDT

The attached document will display columns on screen but not on print (PDF) - I tried with ToT. Firefox is the only one to print colums (other browsers I tried: Opera 9.50.4492, Omniweb 5.6.612.0.92745, Firefox 2.0.0.8 and the latest nightly of Firefox 3) Since I plan to produce PDF that way, this is a blocker for me, but for the casual user, it is major at worst.

Attachments
Simple test. Two pages of lipsum to also test where the columns reset (end of doc or end of page) (10.39 KB, text/html) 2007-10-17 20:21 PDT, David Latapie	no flags	Details
View All Add attachment proposed patch, testcase, etc.

David Latapie

Comment 1 2007-10-17 20:21:05 PDT

Created attachment 16711 [details] Simple test. Two pages of lipsum to also test where the columns reset (end of doc or end of page)

Dave Hyatt

Comment 2 2007-10-17 20:46:54 PDT

Column support is only partially implemented. It's completely disabled when printing right now.

David Kilzer (:ddkilzer)

Comment 3 2007-10-18 05:16:07 PDT

*** Bug 15551 has been marked as a duplicate of this bug. ***

alexandre

Comment 4 2016-04-04 05:48:35 PDT

Hi, columns printing is now implemented properly on Blink since Chromium 49. Any chance to backport their code (don't even know if it is feasible). Very interested to see this implemented. Thanks

Ian Thomas (thelem)

Comment 5 2017-03-13 05:06:26 PDT

Duplicate issues: https://bugs.webkit.org/show_bug.cgi?id=122214 https://bugs.webkit.org/show_bug.cgi?id=156300 Chromium issue including patch: https://bugs.chromium.org/p/chromium/issues/detail?id=99358

Sam Sneddon [:gsnedders]

Comment 6 2021-03-25 16:41:05 PDT

*** Bug 156300 has been marked as a duplicate of this bug. ***

Sam Sneddon [:gsnedders]

Comment 7 2021-03-25 16:41:47 PDT

*** Bug 122214 has been marked as a duplicate of this bug. ***

Brent Fulgham

Comment 8 2022-06-30 09:29:14 PDT

This seems to be tracked by this radar: <rdar://25594228>

Brent Fulgham

Comment 9 2022-07-11 17:01:15 PDT

*** Bug 34610 has been marked as a duplicate of this bug. ***

Stefan Seiz

Comment 10 2024-03-13 08:04:29 PDT

This bug still exists. I'd really appreciate a fix after all the years…

Jason Kichline

Comment 11 2024-04-09 11:42:13 PDT

How has this never been implemented??? I just rebuilt my entire app to be web-based to find out this hasn't been implemented in what, 17 years???

chaffeqa

Comment 12 2025-02-24 07:07:52 PST

please do fix this. its implemented correctly in every other browser

Note You need to log in before you can comment on or make changes to this bug.