1663242 - Image in web page not printed

Status: RESOLVED INVALID

(Core :: Printing: Output, defect)

Description

[Thiagarajan Hariharan]

Attachment: firefox-print-issue.PNG

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:80.0) Gecko/20100101 Firefox/80.0

Steps to reproduce:

Go to
https://chambers.co.uk/wp-content/uploads/2017/06/ChambersJun17_print.html

Select Print... from the firefox menu (shown when clicking on the top right 'burger')

Actual results:

Print preview does not show image of crossword - see attached picture
Printing does not print the image

Expected results:

Print preview should show the image
Printed page should have the image

chrome does not have this problem

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Emilio Cobos Álvarez [:emilio]]

I see the opposite behavior:

• Loading the page doesn't show the image.
• Printing / print preview does.

On chrome, neither does show the image.

I think this is a website issue. The image has a srcset="ChambersJun17_print.png 1x,[e-mail] 2x". So if you're in a hiDPI screen the browser selects the @2x.png version, which doesn't exist: https://chambers.co.uk/wp-content/uploads/2017/06/[e-mail]

Comment 3

[Jonathan Watt [:jwatt]]

Interesting that Chrome doesn't try to use the higher resolution image for printing. Or maybe does, but falls back to trying any of the other images on 404 for any given option?

Comment 4

[Thiagarajan Hariharan]

I'm using Chrome Version 85.0.4183.83 (Official Build) (64-bit)

Comment 5

[Thiagarajan Hariharan]

The image also has src="ChambersAug17.png" attribute. Perhaps that should be used as a fallback.
<img class="GridImg" srcset="ChambersAug17.png 1x,[e-mail] 2x" src="ChambersAug17.png" width="391" height="391">

Comment 6

[Emilio Cobos Álvarez [:emilio]]

That is not how srcset is defined to work, for better or worse :/

Comment 7

[Sean Voisen (:svoisen)]

Sounds like we can close this one as a site issue based on comment 2 and comment 6.