Open
Bug 1651654
Opened 4 years ago
Updated 4 years ago
Black pages on Print preview for icq.com page
Categories
(Core :: Print Preview, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox79 | --- | fix-optional |
firefox80 | --- | fix-optional |
People
(Reporter: csasca, Unassigned)
Details
(Keywords: regression, Whiteboard: [layout:print-triage:p1][print2020])
Attachments
(1 file)
1.34 MB,
image/gif
|
Details |
Affected versions
- Firefox 79.0b5
- Firefox 80.0a1
Affected platforms
- Windows 7 & 10
- macOS 10.15.5
- Ubuntu 20.04
Steps to reproduce
- Launch Firefox
- Access icq.com and shrink the window horizontally as it will trigger the scroll on page
- Open Print Preview
- Select Landscape mode and "Print background" option from Page Setup
Expected result
- Pages are rendered correctly
Actual result
- Pages are black and glitches may occur while scrolling or resizing the window
Regression range
- Will see for a regression.
Additional notes
- The issue can be seen on the attachment
Reporter | ||
Updated•4 years ago
|
Has Regression Range: --- → no
Has STR: --- → yes
Reporter | ||
Updated•4 years ago
|
OS: Windows 7 → All
Reporter | ||
Comment 1•4 years ago
|
||
Tried to see for the regression here and this is what I was able to found. The issue is found somewhere between 2019-08-01 (good) and 2019-08-02 (bad).
The pushlog between them is https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b0124f06562982dce60b820d95aad23afd5cec90&tochange=37229cef2cc79d44470afc9e04016bac8ddd0ae8
Unfortunately mozregression will skip all the builds between these two dates, and can't search any further for this.
Has Regression Range: no → yes
Keywords: regressionwindow-wanted → regression
Updated•4 years ago
|
Severity: normal → S3
Priority: -- → P3
Whiteboard: [layout:print-triage:p1]
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Given other print priorities, we won't fix this in 80 unless we find it affecting more sites.
Whiteboard: [layout:print-triage:p1] → [layout:print-triage:p1][print2020]
You need to log in
before you can comment on or make changes to this bug.
Description
•