Mastodawn

Do I know any @developers devs that work close to #css that I could nerdsnipe into figuring out how chromium could catch up to webkit in so far as a `:host(:has(~ ul li)) {}` selector?

See it in action, here: https://codepen.io/Westbrook/pen/EayLZow

Checkout the #CSSWG convo, here: https://github.com/w3c/csswg-drafts/issues/11859#issuecomment-3834942939

#webComponents developers want all the same `:has()` goodies that anyone can leverage, and you could be the hero we both need and deserve!! 🦸

host has successive sibling with descendant

...

Show thread

Zacky Ma 1d ago

@westbrook I’m AFK so can’t test but wondering if `:host-context()` could achieve the same?

Show thread

westbrook 1d ago

@zacky A great question, and certainly a reason to hope that Chrome wouldn't have much issue getting into this style of selector!

However, these's no _self_ selector in `:host-context()`. Always it's interpreted as:

```css
:host {
.host-context & {
/* You're in a host context. */
}
}
```

It being deprecated, maybe the same intrepid implementor who was going to pull this out of Chromium would be interested in replacing it with extended `:host:has(...)` and `:host(:has(...))` support 🤞

Show thread

Zacky Ma 1d ago

@westbrook Yeah I remember :host:has() was somewhat on track but some people didn’t like the idea of :host(:has()) for the fact that some arbitrary light DOM structure could affect shadow DOM styles. But it would be so useful!

Show thread

westbrook 1d ago

@zacky The fact that it works quite well in WebKit just leaves one wondering what about the Chrome CSS parsing is so...lacking? 🤣

Show thread

Zacky Ma

@westbrook Probably some design on apple.com really really needed that selector 😂