css.types.attr - Incorrect support data for <type-or-unit> of attr()
Nobody has claimed this yet.
- 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?
the test suggest it is supported but bcd says no in chromium
supported: angle | color | custom-ident | image | integer | length | length-percentage | number | percentage | resolution | string | time | transform-function
not supported: url
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
What did you expect to see?
mark it as supported in chrome (should also be 133 version), add missing one and remove not-supported one
add version info for angle | color | integer | length | number | percentage | time
add data for custom-ident | image | length-percentage | resolution | string | transform-function
remove data for frequency | url
Did you test this? If so, how?
in mdn's playground and browser's console
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://developer.mozilla.org/en-US/docs/Web/CSS/attr
https://drafts.csswg.org/css-values-5/#funcdef-attr
https://bugzilla.mozilla.org/show_bug.cgi?id=435426
https://bugs.webkit.org/show_bug.cgi?id=26609
Do you have anything more you want to share?
No response
MDN URL
No response
MDN metadata
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the css.types.attr compatibility data and compare its entries with the MDN CSS attr() page and CSS Values 5 specification. Verify the listed Chromium support in the browser console or MDN Playground, then update the supported and unsupported entries and version information so the data matches the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100