Open
Bug 1147229
Opened 10 years ago
Updated 2 years ago
Background images with negative background-position x are incorrectly printed
Categories
(Core :: Printing: Output, defect)
Tracking
()
People
(Reporter: coq, Unassigned)
References
()
Details
(Keywords: regression)
Attachments
(1 obsolete file)
User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; ASU2JS)
Steps to reproduce:
1) Create html page with only
<div style="height:20px; background:url(Test.gif) -1000px 0px no-repeat;"></div>
2) Test.gif is e.g. 2000px wide, 20px high image
3) Print it to printer or to PDF
Actual results:
The background image in the tag is shifted right (e.g. by 80px, depending probably on the tag width) - it means there is XXpx empty space on the tag left side.
Expected results:
The image should be printed as it is shown on the html page.
Comment 1•10 years ago
|
||
Could you attach a test case or a public url to reproduce the problem?
Flags: needinfo?(coq)
The page is just the <div> and the .gif image, can be tested here:
http://www.treegrid.com/test/MozillaBug1147229/Print.html
and press Ctrl+P to print it
Flags: needinfo?(coq)
Comment 3•10 years ago
|
||
[Tracking Requested - why for this release]: Regression since Firefox35.
Status: UNCONFIRMED → NEW
status-firefox36:
--- → affected
status-firefox37:
--- → affected
status-firefox38:
--- → affected
status-firefox39:
--- → affected
status-firefox-esr31:
--- → unaffected
tracking-firefox38:
--- → ?
tracking-firefox39:
--- → ?
Component: Untriaged → Printing: Output
Ever confirmed: true
Keywords: regression
Product: Firefox → Core
Version: 36 Branch → 35 Branch
Comment 4•10 years ago
|
||
I can reproduce the problem on Windows7 with/without HWA.
Regression window:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=80164e15bd54&tochange=c232720a2847
Regressed by: Bug 1062723
Blocks: 1062723
Comment 5•10 years ago
|
||
Via local build:
Last Good: 5cae10117cf6
First Bad: c232720a2847
Flags: needinfo?(matt.woodrow)
Comment 6•10 years ago
|
||
Regression, tracking.
However, at we shipped 2 releases without getting a bug report sooner, not sure we will block the release for this.
Comment 7•10 years ago
|
||
Matt, do you think you will be able to help during the 38 beta cycle? Thanks
Comment 8•10 years ago
|
||
Tracking for 40 as well since it is likely affected.
status-firefox40:
--- → ?
tracking-firefox40:
--- → +
Comment 9•10 years ago
|
||
Jet, could you find someone to help us on this? Thanks
Flags: needinfo?(bugs)
Comment 10•10 years ago
|
||
Attached is the print output from our color printer using the 3 browsers I have available on Windows 7 using the test supplied in comment 2. Note that none of the browsers print the background image as described in the bug.
Am I missing a key step here?
Flags: needinfo?(matt.woodrow)
Flags: needinfo?(coq)
Flags: needinfo?(bugs)
Comment 11•10 years ago
|
||
(In reply to Jet Villegas (:jet) from comment #10)
> Created attachment 8596095 [details]
> Print output from Firefox, Chrome & IE on Windows
>
> Attached is the print output from our color printer using the 3 browsers I
> have available on Windows 7 using the test supplied in comment 2. Note that
> none of the browsers print the background image as described in the bug.
>
> Am I missing a key step here?
You should turn on "Print Background(colors & images)" from Alt > File > Page Setup
Updated•10 years ago
|
Flags: needinfo?(bugs)
Comment 12•10 years ago
|
||
OK, I was able to see the difference in Print Preview, but the paper output still shows the blank image (same as in my earlier test.) Is that a known bug?
Comment 13•10 years ago
|
||
(In reply to Jet Villegas (:jet) from comment #12)
> OK, I was able to see the difference in Print Preview, but the paper output
> still shows the blank image (same as in my earlier test.) Is that a known
> bug?
Maybe your print driver does not support background image.
I can reproduce this problem with "Canon Bubble-Jet BJ M40" and "Bullzip PDF Printer" at least.
Comment 14•10 years ago
|
||
I was able to reproduce the bug on Firefox 38, but Nightly 40 has the blank background images issue I described, even when "Print Background(colors & images)" is checked. That seems like a more serious and recent regression. I filed bug 1157542 for that.
Comment 15•10 years ago
|
||
Jet, as you can reproduce it, do you think you can help? Thanks
Comment 16•10 years ago
|
||
(In reply to Sylvestre Ledru [:sylvestre] from comment #15)
> Jet, as you can reproduce it, do you think you can help? Thanks
Seth will have a look as he checks out bug 1157542.
Flags: needinfo?(bugs) → needinfo?(seth)
Comment 17•10 years ago
|
||
The browser does not print the pictures set as background in the documents. This solution set such improvement via print setting is far from reasonable. Imagine an enterprise solution where some documents are impressions for approval but are not attested to the production environment?
The programodores can not be conditioned to a user action. After all, what's the problem to implement this feature?
Comment 18•10 years ago
|
||
Too late for 38. It would be nice to have a fix ready for 39.
Comment 19•9 years ago
|
||
Looks like other fixes may have improved this issue but it's still happening.
This may also miss 39 but I would still take a patch if it verifies ok on nightly and aurora.
Comment 20•9 years ago
|
||
Too late for 39 now. Let's make sure this is still affecting 40 and 41. I can't bring myself to drop tracking for this yet.
Comment 21•9 years ago
|
||
Seth, do you think we should still track it? It seems we won't be fixing this anytime soon. Thanks
Comment 23•9 years ago
|
||
I can't reproduce this on Linux, FWIW. (printing URL from comment 2 to PDF, having ticked "Print Background Images" in print dialog's options) I tried Nightly (version 42), as well as release versions 37 and 38.
The left edge of the printed div looks just like my browser window -- there's no empty space between the border and the background-image.
So this might be Windows-only? (At first I was thinking it might've just been fixed elsewhere, except that I can't reproduce it in older Firefox versions which are marked as affected per comment 3.)
Updated•9 years ago
|
Attachment #8596095 -
Attachment is obsolete: true
Comment 24•9 years ago
|
||
This bug is now wontfix for 40. We're going to need to prioritize this and find an owner if it's going to be fixed in 41.
Comment 25•9 years ago
|
||
I'll go ahead and take this during my next pass over regressions, coming soon.
Assignee: nobody → seth
Updated•9 years ago
|
Assignee: seth → nobody
Flags: needinfo?(bugs)
Updated•9 years ago
|
Assignee: nobody → seth
Jet, Beta41 is already in it's final week(s). If we want this fixed for FF41, we might want to find an alternate owner. What do you think?
Flags: needinfo?(bugs)
Comment 27•9 years ago
|
||
(In reply to Ritu Kothari (:ritu) from comment #26)
> Jet, Beta41 is already in it's final week(s). If we want this fixed for
> FF41, we might want to find an alternate owner. What do you think?
No, this bug's severity here doesn't warrant a late fix. Bug 1157542 is the one I was most concerned about. Please untrack this one.
Flags: needinfo?(bugs)
It's not ideal that we are wontfix'ing this bug for a few releases already. In any case, I am moved the tracking fwd from 41 -> 42 with the hope that this issue is fixed in the 42 release cycle.
Comment 29•9 years ago
|
||
We started to track it 5 months ago. I will just stop tracking it for now.
Comment 30•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: seth.bugzilla → nobody
Comment 31•2 years ago
|
||
Redirect needinfos that are pending on inactive users to the triage owner.
:jwatt, since the bug has recent activity, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(seth.bugzilla)
Flags: needinfo?(jwatt)
Flags: needinfo?(coq)
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Flags: needinfo?(jwatt)
You need to log in
before you can comment on or make changes to this bug.
Description
•