mdn / mdn/browser-compat-data

svg.elements.feDistantLight.elevation - low levels of elevation look too dark on firefox

Open
#20,534 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:firefox data:svg needs browser bug p3
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Browser bug (a bug with a feature that may impact site compatibility)

What information was incorrect, unhelpful, or incomplete?

Firefox on Windows 11 (Version 116.0.2 (64-bit) is rendering the effects of feDiffuseLight elevation too darkly compared to Edge and Chrome. It's more apparent for lower values (~10) here are some screenshots of the playground with one circle with elevation=10

Firefox:
firefox

Chrome + edge:
chrome and edge

What browsers does this problem apply to, if applicable?

Firefox

What did you expect to see?

Same brightness as other browsers

Did you test this? If so, how?

Using the playground at mozilla's docs for feDistantLight elevation

https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/elevation#browser_compatibility

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/elevation

MDN metadata
MDN page report details
  • Query: svg.elements.feDistantLight.elevation
  • Report started: 2023-08-13T00:05:28.721Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the MDN elevation page and its playground, reproducing the reported feDistantLight elevation=10 result in Firefox and Chromium-based browsers. Then inspect the related browser-compatibility data entry and determine what evidence is needed for a data change; done means the discrepancy is verified and the appropriate compatibility record or follow-up is clearly identified.

Written by the indexing model from the issue text.

Assessment

Domain
web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.