[css] :has(>child) selector not working in SCSS

[DrSensor]

Issue Type: Bug

a:has(>img) {

}

Will give error:

_{red squiggle at >}

) expectedscss(css-rparentexpected)

_{red squiggle at )}

{ expectedscss(css-lcurlyexpected)

VS Code version: Code - OSS 1.51.1 (e5a624b, 2020-11-12T10:54:25.653Z)
OS version: Linux x64 5.8.18-1-MANJARO

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 3086)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: disabled_software skia_renderer: enabled_on video_decode: unavailable_off vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	7.66GB (0.24GB free)
Process Argv	--no-sandbox
Screen Reader	no
VM	0%
DESKTOP_SESSION	bspwm
XDG_CURRENT_DESKTOP	undefined
XDG_SESSION_DESKTOP	bspwm
XDG_SESSION_TYPE	x11

[DrSensor]

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

[aeschli]

Waiting a bit until this is adopted by browsers.

[Airkro]

same problem

[yume-chan]

same problem

No, yours is another feature.

[DrSensor]

Actually, all > or < symbol inside a bracket has a similiar problem.

[Airkro]

@yume-chan

Maybe not, but they have the same error message

[GEMI]

Anything happening with this issue?

[erictompkins]

We are having a similar issue, but with the + selector followed by a class

.Tabs-button:hover:has(+ .Tabs-button.is-active) {
        border-right: none;
        padding-right: 17px;
}

VS Code shows two errors

• ) expectedcss(css-rparentexpected) for the first red squiggly
• { expectedcss(css-lcurlyexpected) for the second red squiggly

The CSS code is valid and works in Safari.

[controversial]

Having the same issue using :has(+ ...):

Waiting a bit until this is adopted by browsers.

Worth noting that support for :has shipped in Safari 15.4 (on both iOS and macOS) in March, and that it will ship in Chrome 105 at the end of August (see caniuse).

[fabiospampinato]

Can this be put in the next issue's milestone? It's an important feature which shipped in most browsers already, and it's just not supported properly by the editor.

[aeschli]

I've already fixed the has support and it will be in the next milestone.

Duplicate of #147353