Less confused about `max() + calc()`
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
$ lessc --version
lessc 4.1.1 (Less Compiler) [JavaScript]
$ lessc <(echo 'body { padding: max(1em, calc(50vw - 25rem)); } ')
body {
padding: 1em;
}
Expected output:
body {
padding: max(1em, calc(50vw - 25rem));
}
Any subset of the expression (e.g. max(1em, 50vw) or calc(50vw -
25rem)) works fine.
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 reproducing the issue with the shown lessc command and the combined max()/calc() expression. Trace how lessc evaluates this expression compared with the working subsets, then verify that the expected max(1em, calc(50vw - 25rem)) output is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100