Parser bug
See original GitHub issueWhen forming a CSSDeclaration
, the .getProperty
is always formed in lowercase.
This error is critical when we are dealing with variables.
--A != --a
And when call .getExpressionAsCSSString
, the case is respected, as a result, we lose the relationship
Reproducing an error: https://jsfiddle.net/dauhk27r/
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Incident report on memory leak caused by Cloudflare parser bug
It turned out that the underlying bug that caused the memory leak had been present in our Ragel-based parser for many years but...
Read more >Wikipedia:Parser bug reports
To revive discussion, seek broader input via a forum such as the village pump. This is an archive only of bug reports from...
Read more >Parse Error: What It Is and How to Fix It - Lifewire
A parse error is an error message you sometimes get on Android devices when an app fails to install. The message itself is...
Read more >URL Parsing-Library Bugs Allow DoS, RCE, Spoofing & More
They occur when a web application accepts a user-controlled input that specifies a URL that the user will be redirected to after a...
Read more >HTML parser bug triggers Chromium XSS security flaw
A “crazy” parser bug potentially leading to XSS exploits has been patched by Chromium developers. The vulnerability was reported in July 2021 to ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Input:
Output:
var(--A)
- variable--A
not foundThere are no other problems. Many thanks!