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

Clicking a link vs. typing the link in the address bar gives different SVG output.

  • 2 odgovora
  • 1 ima ovaj problem
  • 4 prikaza
  • Posljednji odgovor od FredMcD

more options

I have a web app that uses SVG to render. There's a problem with SVG gradient fills rendering when I type the URL of the application that doesn't occur when I navigate to the site via a bookmark.

If you navigate to https://www.draw.io?ff=1 you'll see the correct result, an SVG rect with a gradient fill. If you manually type that URL, the fill fails.

I've tested this on FF 3.6, 18, 29 and 31 on Windows 7, OS X 10.9 and Linux Mint 17, they all show this behaviour.

I found this thread that might be related and I've tested in safe mode with the cache cleared and that doesn't help: https://support.mozilla.org/en-US/questions/1005522?esab=a&as=aaq

I have a web app that uses SVG to render. There's a problem with SVG gradient fills rendering when I type the URL of the application that doesn't occur when I navigate to the site via a bookmark. If you navigate to https://www.draw.io?ff=1 you'll see the correct result, an SVG rect with a gradient fill. If you manually type that URL, the fill fails. I've tested this on FF 3.6, 18, 29 and 31 on Windows 7, OS X 10.9 and Linux Mint 17, they all show this behaviour. I found this thread that might be related and I've tested in safe mode with the cache cleared and that doesn't help: https://support.mozilla.org/en-US/questions/1005522?esab=a&as=aaq

Izabrano rješenje

We've solved this, the problem was the way we redirected to https using window.location.protocol. We're now using window.location.href and it works.

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (2)

more options

Odabrano rješenje

We've solved this, the problem was the way we redirected to https using window.location.protocol. We're now using window.location.href and it works.

more options

Hello,

I am glad to hear that your problem has been resolved. If you haven't already, please select the answer that solves the problem. This will help other users with similar problems find the solution more easily.

Thank you for contacting Mozilla Support.