This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

SVG animation do not properly display strokes

  • 6 replies
  • 1 has this problem
  • 8 views
  • Last reply by TyDraniu

more options

On 2 websites where we have many SVG illustrations, the strokes that were previously (and on other browsers) well displayed, are now vertical lines that go through the whole website! There is no issue with full shapes, only with strokes but we also have dashed strokes animated so it's not possible to vectorize all the strokes.

On 2 websites where we have many SVG illustrations, the strokes that were previously (and on other browsers) well displayed, are now vertical lines that go through the whole website! There is no issue with full shapes, only with strokes but we also have dashed strokes animated so it's not possible to vectorize all the strokes.
Attached screenshots

All Replies (6)

more options

Can you provide a link to the working example of the issue?

more options
more options

Intico is OK, but sth is wrong with this file: https://www.adneom.com/wp-content/themes/ptc/dest/css/main.css?ver=1.0

You've to check your latest changes.

more options

Thanks for the help!

For Intico, we have changed the strokes to full elements (which is not a solution for me) but for the file https://www.adneom.com/wp-content/themes/ptc/dest/css/main.css?ver=1.0 there is no issue in Chrome and there wasn't any issue in Firefox before yesterday.

Modified by Clairedomi

more options

For me, after deleting this file, the issue magically dissapears. I don't know why.

Modified by TyDraniu

more options

On the other hand, it may be our bug.

https://bugzilla.mozilla.org/show_bug.cgi?id=1538666