Opened 17 years ago
Closed 16 years ago
#5794 closed defect (worksforme)
FC6 firefox printing problem
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | needinfo firefox |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
For some reason since updating to Fedora Core 6 I have noticed that although the print preview looks ok, when printing from firefox only the first letter of each heading is actually printed! The main body of a ticket is still printed but just not the full titles.
Attachments (0)
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
| Keywords: | needinfo firefox added |
|---|
This also works fine for me using Firefox 2.0. Try upgrading your Firefox version. Does that fix your problem?
comment:3 by , 17 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Relying on the 'worksforme' feedback given by sid.
comment:4 by , 17 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
i'm still not able to print on fedora 8 with firefox-2.0.0.13-1.fc8 any trac wiki pages:-( neither on linux nor on windows nor with IE:-(
comment:5 by , 17 years ago
Is that happening just for your own Trac site, or for others as well?
e.g. can you print Wiki pages from this Trac?
Also, does this problem also happen for other pages (like tickets) or exclusively for Wiki pages?
comment:6 by , 16 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | reopened → closed |
No feedback given (for what was likely not a Trac issue anyway).
My first instinct: not a Trac problem but a Firefox/FC6 problem. You could inspect the HTML source code and CSS Trac outputs and compare it to pages that do print normally to see if Trac does anything out of the ordinary to the headers that makes that specific combination of browser and OS freak out when printing. I suggest hacking at the HTML/CSS with something like the Web Developer extension for firefox until it does print normally and then figure out whether the changes you had to make were necessary either because the original code was weird or because the browser handled it wrongly.