Print preview doesn't show table lines after first page for table that spans multiple pages
Categories
(Core :: Printing: Output, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | wontfix |
| firefox72 | --- | wontfix |
| firefox73 | --- | fix-optional |
| firefox74 | --- | fix-optional |
| firefox96 | --- | affected |
People
(Reporter: jbovey, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(2 files)
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Updated•8 years ago
|
Comment 4•8 years ago
|
||
Updated•8 years ago
|
Comment 5•8 years ago
|
||
Comment 7•8 years ago
|
||
Comment 8•8 years ago
|
||
Comment 9•8 years ago
|
||
| Reporter | ||
Comment 10•8 years ago
|
||
Comment 11•8 years ago
|
||
| Reporter | ||
Comment 12•8 years ago
|
||
| Reporter | ||
Comment 13•8 years ago
|
||
Comment 14•8 years ago
|
||
Comment 15•7 years ago
|
||
Timea says in bug 1394249 comment 58:
Tested on latest Nightly 66 on Windows 7 x64 and the borders are still not rendered in print preview. Used this reduced testcase from Bug 1392028 : https://bug1392028.bmoattachments.org/attachment.cgi?id=8906309
It seems to work fine for me when I test it in Nightly on Linux,
so I guess there's a platform specific issue still lurking on Windows...
Comment 16•7 years ago
|
||
(In reply to Mats Palmgren (:mats) from comment #15)
Timea says in bug 1394249 comment 58:
Tested on latest Nightly 66 on Windows 7 x64 and the borders are still not rendered in print preview. Used this reduced testcase from Bug 1392028 : https://bug1392028.bmoattachments.org/attachment.cgi?id=8906309
It seems to work fine for me when I test it in Nightly on Linux,
so I guess there's a platform specific issue still lurking on Windows...
I am on FF 64, Windows 7 x86, and the testcase prints correctly (borders are rendered both in print preview and in the output pdf).
Comment 17•7 years ago
•
|
||
Reproduced the issue on Windows 10 x64 too on latest Nightly, latest Beta 65.0b9 and Firefox Release 64. Recording of the issue: https://streamable.com/512fu
Comment 18•7 years ago
|
||
(In reply to Timea Babos from comment #17)
Reproduced the issue on Windows 10 x64 too on latest Nightly, latest Beta 65.0b9 and Firefox Release 64. Recording of the issue: https://streamable.com/512fu
Does the issue affect print preview only, or the print output too?
Comment 19•7 years ago
|
||
Only Print Preview is affected, if I actually print it out it looks just fine.
Comment 20•7 years ago
|
||
(In reply to Timea Babos from comment #19)
Only Print Preview is affected, if I actually print it out it looks just fine.
Then I think your problem is not this bug or a related one but the quality of print preview in general. As I recall, print preview in Firefox has never been very reliable. I myself can see the borders disappear and reappear if I zoom in or out. At the default zoom (Shrink to Fit) some borders are not shown. If I zoom in enough, say 150%, all borders appear.
Comment 21•6 years ago
|
||
Reproduced the issue on latest Nightly 71.0a1 (2019-10-15) using Windows 7 x64.
Comment 22•6 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Updated•6 years ago
|
Comment 23•6 years ago
|
||
Reproduced the issue on latest Nightly 72.0a1 (2019-11-06) using Windows 8.
Updated•6 years ago
|
Comment 24•6 years ago
|
||
Reproduced the issue on latest Nightly 73.0a1 (2019-12-10) (Build id: 20191209215019).
Comment 25•6 years ago
|
||
Happy to take a patch for this in 74 or potentially in 73, but I'm marking the bug fix-optional to remove it from weekly triage.
Comment 26•6 years ago
|
||
On Firefox 71.0 (64 bitų) on Ubuntu 18.04 the top borders are still not rendered after initial page in print preview (also on actual print). Used this reduced testcase from Bug 1392028 : https://bug1392028.bmoattachments.org/attachment.cgi?id=8906309
Comment 27•6 years ago
|
||
I've seen this issue on Windows 10 and Firefox version 74.0a1 (2020-01-13) (64-bit).
Comment 28•6 years ago
|
||
I am removing the regression keyword as the regression happened several years ago and we wouldn't back out the original regressor, there is no need to have this bug in regression triage every week.
Updated•4 years ago
|
Updated•3 years ago
|
Comment 29•3 years ago
|
||
I am still getting this issue on Firefox 110.0 64 Bit, Windows 10. The table displays properly on other browsers
Description
•