components are skiping the parent priority when running on build mode to find their width
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
that's basically it, the issue is described there, more information about it:
in the following structure, where the input has a width of 85% it is taking the width of the nth parent instead of the direct one.
given this structure the input element is given the relative width according to the width of the div with class login-content container ->
<div class="width:100vw">
<div class='width:50%'>
<div class= 'width:100%'>
<input class='width:85%'
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 from the nested-width example in the issue and reproduce the behavior in build mode using the React documentation site. Trace how the input width is resolved through its parent elements; done means the input uses the direct parent width rather than an nth ancestor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100