Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

Firefox 6.02 prints background color even though this setting turned off.

  • 2 odpovede
  • 3 majú tento problém
  • 15 zobrazení
  • Posledná odpoveď od Laurie_R

more options

I use a off-white background color in Windows to reduce glare. With previous Firefox versions, I could print without this background color showing in the print. The Print Background & Images setting is Off in Page Setup/Format tab, but the background color still comes through when I print a page. How do I fix this problem?

I use a off-white background color in Windows to reduce glare. With previous Firefox versions, I could print without this background color showing in the print. The Print Background & Images setting is Off in Page Setup/Format tab, but the background color still comes through when I print a page. How do I fix this problem?

Všetky odpovede (2)

more options

I have found a clumsy work around to this.

If you set the background color to anything, then it doesn't print (comes out as white). The default background color seems to only print if the webpage has not specified a background color.

I was able to edit local HTML pages by changing the <body> tag to <body bgcolor=#CCCCCC>. This makes the pages a light gray which reduces the glare, but it doesn't print.

That said, specifying the page color in css didn't work, but that is probably more because I don't really know what I am doing in css.

Not much use for printing from an on-line webpage though.

hope it is some help.

more options

Thanks for trying! I hope someone else can come up with a better suggestion. This problem never came up in previous versions, so it is unique to 6.02 and 7.01 (installed since I first posted this question).