Parent components ignore min-* and max-* values.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 18.9k
- Forks
- 1.6k
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I noticed that when both the min-height and height properties are set, if the min-height is higher than the height, then the siblings will be positioned as if the element height was its min-height (which is what happens in browsers), but the parent container will use the height instead (which means it will be smaller than it should). I believe the opposite is also true (a max-height lower than the height).
Browser rendering:
https://jsfiddle.net/Lrqeng4b/
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 by comparing the browser rendering in the linked JSFiddle with the Yoga rendering reproduction. Trace parent sizing for children whose height conflicts with min-height or max-height, and consider the issue done when the parent dimensions match browser behavior in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100