After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 541580 - Printed Content is very small
Printed Content is very small
Status: RESOLVED DUPLICATE of bug 541168
Product: epiphany
Classification: Core
Component: Printing
2.22.x
Other All
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-04 18:18 UTC by Arthur Taylor
Modified: 2008-07-04 19:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Screenshot of problem output (25.19 KB, image/png)
2008-07-04 18:19 UTC, Arthur Taylor 		Details

Description Arthur Taylor 2008-07-04 18:18:11 UTC 
Please describe the problem:
When trying to print a web page, the page headers and footers are created, and the page content is almost microscopic.

Steps to reproduce:
1. Go to a web page
2. Do File->Print
- or -
2. Do File->Print Preview


Actual results:
A page is generated which contains normal sized footers and headers, but the content which should fill the body of page is about 5x5mm at the top left

Expected results:
A page is generated which contains normal sized footers, headers and content nicely scaled in the middle

Does this happen every time?
Yes.

Other information:
This bug started to occur for me after building against xulrunner-1.9 instead of 1.8
Comment 1 Arthur Taylor 2008-07-04 18:19:35 UTC 
Created attachment 114000 [details]
Screenshot of problem output

Note the google search page under the "u"
Comment 2 Arthur Taylor 2008-07-04 18:20:05 UTC 
May be related to http://bugzilla.gnome.org/show_bug.cgi?id=528999 ?
Comment 3 Cosimo Cecchi 2008-07-04 19:12:02 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 541168 ***