jaraco / jaraco/cssutils

Calc with internal parentheses being deleted.

Open
#5 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Python
Stars
92
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Pardon the unusually high specificity of this bug, but this has been a serious blocker for me, and has cost me most of a day.

Basically, from my research I've found that any line of CSS including parentheses inside a calc statement will be removed. To test, all I'm doing with my CSS currently is parsing and printing it (Using the current v2.2.0 version, ofc):

stylesheet = cssutils.parseString(css_contents)
print(stylesheet.cssText.decode("utf-8"))

In my findings, even lengthy calcs like this will be left alone: font-size: calc(15px * 100vw - 600px / 1320);, but the moment any brackets are introduced it will fail, like this line: font-size: calc((100vw - 600px) * 10);.

Functions like this are supposedly meant to be handled according to the documents linked in the README, look at Example 29 for particulars. Regarding that same example, I've also tried nested calcs in the same fashion, to no avail: font-size: calc(calc(100vw - 600px) * 10);.

Basically what I'm asking, is if there's any way for this bug to be fixed or worked around? Ideally, I'd love something I can do today, to either skip validating these lines or to find a way to get them to pass without changing the meaning.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the parseString entry point and reproduce the reported output using the two calc examples, including the nested calc. Compare the parser's handling of parentheses with the CSS Values Level 4 calc examples linked from the README; done means parsing and printing preserves the meaning of these declarations instead of deleting them.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.