Intrinsic & Extrinsic Sizing - Incorrectly marked as supported
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What information was incorrect, unhelpful, or incomplete?
Currently, MDN browser compat data reports Intrinsic & Extrinsic Sizing as fully implemented.
What did you expect to see?
I expected the truth that these are not fully implemented across Chrome and Firefox.
Did you test this? If so, how?
I didn't test it. This is very complicated.
I encountered min-height: min-content not working in Firefox and Chrome against what BCD reports, while in Safari it does. I didn't test any further, since there seem to be a lot of bugs around this. Also there are more sizing values (max-content, fit-content) as well as sizing properties (max-height, min-width, max-width, height, width) that complicate things further.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
The Caniuse-own entry lists some bugs.
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 with the linked Caniuse intrinsic-width entry and compare it with the browser compatibility data for intrinsic sizing. Review the reported behavior for min-content, max-content, and fit-content across the affected properties and browsers; done means the data no longer reports full support where the evidence shows it is incomplete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- documentation, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100