JakeQZ

Though `RuleSet` shouldn't need to know about `DeclarationBlock`, as the latter is a subclass (and if it does, there's a circular dependecy). Instead it should have methods that `DeclarationBlock` can...

> * A (possibly-empty) interface `RuleOrDeclarationBlock` (for want of a better name) can be introduced for type-strictness `RuleSetItem`?

Ref: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_nesting

> > `RuleSet::parseRuleSet()` would need an extra Boolean parameter to permit declaration blocks as well as property-value rules: > > I consider boolean parameters that change the general way a...

> > * A (possibly-empty) interface `RuleOrDeclarationBlock` (for want of a better name) can be introduced for type-strictness > > `RuleSetItem`? Actually, this isn't going to work like that (at...

> When it comes to rendering, it won't matter if, say, all the `Rules` are output before all the `DeclarationBlock` children, because (I think) the children can't match any of...

> Maybe we might put this on the back-burner and tackle this after [a rewrite](#1189). I'd prefer to get this in sooner, with more minimal refactoring, since it's already part...

> We should look into the spec to see what we should do to distinguish properties from selectors. > These are the specs explaining the algorithms: https://www.w3.org/TR/css-syntax-3/ I've picked out...

> [``](https://www.w3.org/TR/css-syntax-3/#typedef-eof-token) > > - [Extend](https://infra.spec.whatwg.org/#list-extend) decls with rules, then return decls. This doesn't seem to deal with the ordering issue either.

> Do you think it's something you can fix? Because we have a few of these cases and it breaks the rendering Hi @ocoste, We will be able to implement...