Open Bug 1897723 Opened 1 year ago Updated 6 days ago

www.slowboring.com - Print previews display copyright footer over bottom text on first page

Categories

(Web Compatibility :: Site Reports, defect, P2)

Firefox 128
Desktop
Windows 10

Tracking

(Webcompat Priority:P3, Webcompat Score:1, firefox126 affected, firefox128 affected, firefox138 affected)

Webcompat Priority P3
Webcompat Score 1
Tracking Status
firefox126 --- affected
firefox128 --- affected
firefox138 --- affected

People

(Reporter: azlata, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:needs-contact, webcompat:platform-bug)

User Story

platform:windows,mac,linux
impact:content-missing
configuration:general
affects:some
diagnosis-team:layout
user-impact-score:9

Attachments

(2 files)

Environment:
Operating system: Windows 10
Firefox version: Firefox 126.0/128.0a1 (2024-05-19)

Steps to reproduce:

  1. Access https://www.slowboring.com/p/the-geopolitical-underpinnings-of either logged in or in a new session. Scroll down a bit and close the "sign in" / "continue reading" dialog if it is present.
  2. Print (Ctrl+P)
  3. Observe the first page.

Expected Behavior:
No footer should be displayed on top of the content.

Actual Behavior:
Print previews display copyright footer over bottom text on first page

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in Firefox Nightly, Firefox Release
  • Does not reproduce in Chrome

Created from https://github.com/webcompat/web-bugs/issues/137149

OS: Unspecified → Windows 10
Hardware: Unspecified → Desktop
Version: unspecified → Firefox 128
Severity: -- → S3
User Story: (updated)
Priority: -- → P2

note that this issue impacts printing on most Substack blogs or sites that use Substack articles, not just the website in the subject line.

User Story: (updated)

The copyright footer here is absolutely positioned:

.footer-wrap .footer {
  position: absolute;
  bottom: 0;

So this may be a version of bug 267029 or similar. I want to come up with a reduced testcase to be sure, though. My initial attempt was this, but the footer ends up on the last-page as-expected:
[EDIT: removing data URI since it had a typo and didn't repro the bug anyway]

Attached file testcase 1 (reduced)

Yeah, I think this is a version of bug 267029. Here's a reduced testcase based on the linked article.

If I print-preview this testcase in Firefox (portrait us-letter paper size), I see the Abspos Div at the bottom of page 1, when really it should be on page 2 (at the very end of the bordered area).

Webcompat Priority: --- → P3
Webcompat Score: --- → 1

The issue is still reproducible

Tested with:

Browser / Version: Firefox Nightly 138.0a1 (2025-03-23) (64-bit)
Operating System: Windows 10 PRO x64

Depends on: 1956112

Thanks! I spun off a new platform-bug with a testcase based on the one attached here.

(In reply to 13hu from comment #2)

note that this issue impacts printing on most Substack blogs or sites that use Substack articles, not just the website in the subject line.

Adding needs-contact to see if we can reach out to Substack to see if they can fix this.

One workaround that they could deploy would be the following to cancel out their rule quoted in comment 3 when printed:

@media print {
  .footer-wrap .footer {
    position: static;
  }
}

We could deploy that^ as a sitepatch, too -- I confirmed that it fixes the issue here and successfully puts the copyright notice at the bottom of the printed output. However, sitepatches here are a little tricky since (as in this slowboring.com example) the affected pages aren't all part of the same domain that we can target.

(With that fixed, there's another unrelated issue, too - a little bit of content seems to get clipped/pushed-off-the-page on the right side of the article -- but I can reproduce that right-side-clipping issue in Safari/WebKit as well, for what it's worth.)

reporter here - thanks for looking into this.
If you're doing a sitepatch, would probably be good to do it for *.substack.com

Is this also a W3C webcompat issue with how firefox handles printing of absolute position though, since Chromium/Safari does not have this issue?

Best,

ah I see that's bug 1956112

User Story: (updated)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: