Parsing RGBA hex codes fails (feature from CSS Color Module 4)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by reproducing the issue with cssutils.parseString("body { color: #00808080; }") and trace the parser path for color values. Check the existing handling of CSS Color Module 4 hex notation; done means 8-digit RGBA hex colors parse without ERROR-level logs or property syntax errors.
Written by the indexing model from the issue text.
Description
When a stylesheet with RGBA hex codes is parsed, it triggers ERROR-level logs.
Quick proof from an interactive Python session using cssutils==2.15.0:
$ python
Python 3.12.3 (main, Jun 19 2026, 12:46:00) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cssutils
>>> cssutils.parseString("body { color: #00808080; }")
ERROR PropertyValue: Missing token for production Choice(ColorValue, Dimension, URIValue, Value, variable, MSValue, CSSCalc, function): ('HASH', '#00808080', 1, 15)
ERROR No content to parse.
ERROR PropertyValue: Unknown syntax or no value: #00808080
ERROR CSSStyleDeclaration: Syntax Error in Property: color: #00808080
cssutils.css.CSSStyleSheet(href=None, media=None, title=None)
CSS Color Module 4 documents that as a supported syntax (8-digits): https://drafts.csswg.org/css-color/#hex-notation
I guess it's linked to #29 which covers a generic need to implement features from the CSS Color Module 4.
- Dominant language
- Python
- Stars
- 92
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from jaraco/cssutils
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Wrong specificity Openhelp wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·