Starting a CSS rule with > breaks styling without producing an error

[maxlath]

Describe the bug

Starting a CSS rule with > at the <style> root breaks the CSS rules from that point, without producing an error. Consequently, the developer is let wondering why those CSS rules have no effect.

I don't see how a child combinator (>) could be valid at a component root, so this should probably generate an error. The same is true for the sibling combinator (+), but that one at least already produces a Unused CSS selector warning, and does not result in the following CSS rules to be dropped.

Reproduction

See https://svelte.dev/repl/b8551c675fbd4f4e9b174d3f11000512?version=3.48.0

Notice the broken CSS output:

> >

Logs

No response

System Info

Svelte v3.48.0

Severity

annoyance

[Conduitry]

This is fixed in 3.50.0 - https://svelte.dev/repl/b8551c675fbd4f4e9b174d3f11000512?version=3.50.0