mdn / mdn/browser-compat-data

CSS <color> data type, color functions - "none" keyword not properly supported by any browser at this time

Open
#22,817 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple data:css 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?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

Support for none is not a data point here (not sure what the correct vocabulary is here). It should be. No browser supports none fully.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Legacy Edge (12-18), Safari, Node.js, Deno

What did you expect to see?

I expect to see none listed in the compatibility table on MDN docs here:
https://developer.mozilla.org/en-US/docs/Web/CSS/color_value#browser_compatibility

And wherever else is appropriate

Did you test this? If so, how?

See these two discussions with experts on the subject:
https://bugzilla.mozilla.org/show_bug.cgi?id=1886570#c10
https://github.com/color-js/color.js/discussions/495#discussioncomment-8872601

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?

If someone can instruct me on how to add/edit which files, I can submit the PR.

MDN URL

No response

MDN metadata

No response

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 CSS color compatibility table at the linked MDN page, then compare its current data with the Mozilla Bugzilla and color.js discussions. Locate the corresponding browser-compatibility data entry and determine how the none keyword should be represented. Done means the incomplete support information is accurately reflected for the affected browsers and appears wherever the data belongs.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.