Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

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

  • 2 odgovora
  • 3 imaju ovaj problem
  • 15 prikaza
  • Posljednji odgovor 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?

Svi odgovori (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).