scuffed @custom-variant behavior

[tizu69]

Registering a v4 custom-variant with a nested (pseudo-)selector causes "at-rule or selector expected". It compiles just fine.

@custom-variant poi {
	&:hover,
	&:focus-visible {
		@slot;
	}
}

The last 2 errors go away on removing the @slots ;. However, this is not a viable option, as Prettier adds it back.

---

Oddly enough, it seems to replace this with... whatever this mess is.

---

This happens because the Regex matches up to a ;: (\s+[^;]+). I'm not sure what the point of this is.
There is another matcher that uses { right below, but it never gets called, as the matcher with the ; already
replaces everything up to the slot semicolon.

Removing it seems to have done the trick. All tests pass with this change.

---

... now this throws. Even if I restore the original extension. lovely.

The space was added by Prettier, but this also happens without it. Adding other spaces restores it to [ *], so my PR allows a space before *.

It seems like it doesn't like *. Replacing it with _ in the virtual document works fine. All tests pass with this change.

---

I'd like to work on this. I'll follow up with a PR in a bit.

[gustavopch]

The problem also happens with this snippet from the documentation.

@custom-variant supports-grid {
  @supports (display: grid) {
    @slot;
  }
}

[tizu69]

The problem also happens with this snippet from the documentation

@gustavopch is this with the fixes applied, or original extension?

[gustavopch]

The original extension. Didn't try your patch.

[tlgreg]

It has been happening since 0.14.4, seems like the shorthand fix might have broken the long form. #1183

[thecrypticace]

yep it did — sorry! Obviously I need to add automated tests for the css language mode this week.

Gonna push a fix out today.