mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-05-02 01:08:48 +00:00
79a30c209d
When parsing these, <number> is allowed anywhere that would usually allow a <length>, <length-percentage>, or <angle>. The spec is not clear on exactly how this should work (see https://github.com/w3c/svgwg/issues/792 ) so I'm using some artistic license until things are clearer: - If we expected a <length>, treat the <number> as pixels. - If we expected an <angle>, treat the <number> as degrees. - Only allow direct <number> tokens, not calc() or other functions. From what I can tell this is what the spec *intended* but I may be very wrong. In any case, telling the ParsingContext whether we're parsing one of these attributes is a cleaner approach and more correct than temporarily enabling quirks mode, which we did previously. |
||
|---|---|---|
| .. | ||
| Block.cpp | ||
| Block.h | ||
| ComponentValue.cpp | ||
| ComponentValue.h | ||
| Declaration.cpp | ||
| Declaration.h | ||
| DeclarationOrAtRule.cpp | ||
| DeclarationOrAtRule.h | ||
| Dimension.h | ||
| Function.cpp | ||
| Function.h | ||
| GradientParsing.cpp | ||
| Helpers.cpp | ||
| MediaParsing.cpp | ||
| Parser.cpp | ||
| Parser.h | ||
| ParsingContext.cpp | ||
| ParsingContext.h | ||
| Rule.cpp | ||
| Rule.h | ||
| SelectorParsing.cpp | ||
| Token.cpp | ||
| Token.h | ||
| Tokenizer.cpp | ||
| Tokenizer.h | ||
| TokenStream.h | ||