rust-cssparser
rust-cssparser copied to clipboard
servo
Rust implementation of CSS Syntax Level 3
In #165, this input `3E833` is parsed as a `Token::Number` whose value is `std::f32::INFINITY`, which serializes as `inf`. We should definitely not serialize any number as `inf` (maybe an arbitrary...
Found this [while fuzzing](https://github.com/rust-fuzz/targets/pull/76). ```rust extern crate cssparser; use cssparser::ToCss; fn main() { let input = "\\\n3:\'\\\x0c"; println!("input:\n\t{:?}", input); let mut parser_input = cssparser::ParserInput::new(input); let mut parser = cssparser::Parser::new(&mut parser_input);...
I've created a little tool https://github.com/mothsART/cssoptiadvisor (not really mature, just a toy) Lightningcss and other minification tools don't find duplicates on keyframes. It seems difficult to analyze all the values...
Make crate no_std while keeping it backwards compatible with a default `std` feature enabled(only used to impl Error for ParseError).
If a long string of hex digits are passed to unicode-range, the code tries to parse them into a number before checking whether there are more than the 6 digits...
It seems that the dependencies of this crate all support no_std. It seems that it is possible for this crate to support no_std. Is there any hidden problem? If it...
Hey This is a hacky fix for adding support of legacy `*` prefixes to `cssparser`. Currently this fails to be parsed: ```css p { *color: red; } ``` And there...
According to CSS forward-compatible parsing rules, if a CSS declaration fails to parse the parser should forward until whichever is closer of EOF and a semicolon then resume parsing. cssparser...
While fuzzing the cssparser fuzz target I encountered a stack overflow leading to a core dump. The overflow occurs when the input contains ~17500 (or more) opening brackets, i.e., `(`,...
