Open
Bug 1657906
Opened 4 years ago
Updated 3 months ago
Text is displayed as cut-off in both print preview and print job's output for a specific bbc article
Categories
(Core :: Printing: Output, defect)
Core
Printing: Output
Tracking
()
People
(Reporter: emilghitta, Unassigned)
References
()
Details
(Whiteboard: [print2020])
Attachments
(1 file)
8.97 MB,
image/gif
|
Details |
Affected versions
- 81.0a1 (BuildId:20200804215246)
- 80.0b5 (BuildId:20200806203447)
- 79.0 (BuildId:20200720193547)
- 78.1.0esr (BuildId:20200722151235)
Unaffected versions
- 68.11.0esr (BuildId:20200720181548)
Affected platforms
- Windows 10 64bit
- Ubuntu 18.04 64bit
- macOS 10.14
Steps to reproduce
- Launch Firefox.
- Access the following link
- Open the print preview.
- Print the article to paper or to file.
Expected result
- The article is printed without any issues.
Actual result
- The article’s text is being displayed as cut-off inside print preview and inside both print to file output & print to paper output.
Regression Range
- It seems that, on older builds (68.11.0esr included), the article’s text was not displayed at all inside the print preview nor printed to file or to paper. It seems that recent changes have made the text to be visible but is displayed as cut-off on both print preview and on actual print output. I'll search for that particular fix as soon as time permits.
Notes
- Please observe the attached screencast for further information regarding this issue.
- Chrome doesn't seem affected and the article's text is successfully displayed in both print preview & print job output.
- [Suggested Severity] I'm not sure if this issue will be encountered on other webpages that are more often printed, but the outcome here is pretty ugly and there doesn't seem to be a workaround in printing this article without the text being cut-off. I think that marking this as an S2 or S3 fits here.
Comment 1•4 years ago
|
||
Triaging as S3, and putting in the [print2020] bucket.
(I'm also clearing "firefox-esr68:unaffected" status because that gives the implication that this regressed in the 68-78 timeframe. Really, things improved here in that timeframe, but are still imperfect; the article text now shows up but is partly cropped. I would bet bug 1622935 is what improved things in that timeframe, or some related bug.)
Updated•4 years ago
|
Has STR: --- → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•