mdn / mdn/browser-compat-data

`css.types.ratio.number_value` has support, none is mentioned

Open
#25,034 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

css.types.ratio.number_value reports only implementation behind a flag in Firefox. The description is "Accepts a single <number>; as a value." This is in line with the spec definition of ratio, which accepts a single number, defaulting to 1.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Safari

What did you expect to see?

Some support, but I'm unsure of when it was added. Alternatively, if we're unable to determine when this was added, it may make most sense to just remove this key.

Did you test this? If so, how?

https://codepen.io/jamessw/pen/abePENz

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/CSS/ratio#browser_compatibility

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 MDN ratio browser-compatibility page and the linked CSS Values 4 ratio specification, then compare the reported behavior using the supplied CodePen test. Determine whether browser support can be dated reliably or whether the number_value key should be removed; done means the compatibility data accurately reflects the finding.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, json
Domain
documentation, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.