Avatar for Username

Search 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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

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

  • 2 àwọn èsì
  • 1 ní ìṣòro yìí
  • 4 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ 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

Ọ̀nà àbáyọ tí a yàn

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.

Ka ìdáhùn ni ìṣètò kíkà 👍 1

All Replies (2)

alderg
alderg Ìbéèrè olóhun
more options

Ọ̀nà àbáyọ Tí a Yàn

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.