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 objects with the <feSpecularLighting> filter effect do not display

  • 2 replies
  • 1 has this problem
  • 2 views
  • Last reply by cor-el

more options

When I open a Scalable Vector Graphics (.svg) file in Firefox, any objects having filters that contain the <feSpecularLighting> filter primitive, do not display at all and in rare cases, even causes Firefox to crash.

For example:

It should render like this:

When I open a Scalable Vector Graphics (.svg) file in Firefox, any objects having filters that contain the <feSpecularLighting> filter primitive, do not display at all and in rare cases, even causes Firefox to crash. For example: *http://upload.wikimedia.org/wikipedia/commons/e/ee/Video_game_health_bar.svg It should render like this: *http://upload.wikimedia.org/wikipedia/commons/thumb/e/ee/Video_game_health_bar.svg/3000px-Video_game_health_bar.svg.png

Modified by cor-el

Chosen solution

In order to get the SVG file to render like the PNG, you need to edit kernelUnitLength from 0.01 to approximately 1.0 (or delete it). Not sure whether something might have changed in how Firefox handles this attribute to cause such a drastic difference.

I should test in a clean profile to see whether I get the same result...

Edit: Same result in a clean profile, i.e., no extensions or settings changes from factory default.

Read this answer in context 👍 1

All Replies (2)

more options

Chosen Solution

In order to get the SVG file to render like the PNG, you need to edit kernelUnitLength from 0.01 to approximately 1.0 (or delete it). Not sure whether something might have changed in how Firefox handles this attribute to cause such a drastic difference.

I should test in a clean profile to see whether I get the same result...

Edit: Same result in a clean profile, i.e., no extensions or settings changes from factory default.

Modified by jscher2000 - Support Volunteer

more options