Join the AMA (Ask Me Anything) with Firefox leadership team to talk about Firefox priorities in 2024. Mark your calendar! Thursday, June 13, 17:00 - 19:00 UTC.

Avatar for Username

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

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

  • 2 svar
  • 1 har dette problem
  • 10 visninger
  • Seneste svar af FredMcD

alderg
alderg
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

Valgt løsning

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.

Læs dette svar i sammenhæng 👍 1

Alle svar (2)

alderg
alderg Spørgsmålsstiller
more options

Valgt løsning

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.

FredMcD
FredMcD
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.