:has doesn't work

[daelmaak]

We are using JSS in react to define rulesets with selectors like these

const useStyles = createUseStyles((theme) => ({
  category: {
    '&:has(input:checked)': {

In tests we use jsdom@26.1.0 to render components with those styles.

For some reason I don't completely understand, the selector that gets parsed in https://github.com/dperini/nwsapi/blob/master/src/nwsapi.js#L1569 ends up looking like 'input#9yecS.input-0-2-453 input:checked' and the parsing result ends up being:

[
  "input",
  "",
  "",
  "yecS.input-0-2-453 input:checked",
]

This produces invalid selector and when applied produces DOMException.

The interesting thing is that if we remove :has from the original rule, there is no such problem.

[dperini]

@daelmaak
thank you for the report... this will take a bit more time but was already passing the wpt tests in one of the recent releases.
The problem here seems to be bound to changes to the :scope resolver which was previously considered a transformation while now it is going to be implemented as a real pseudo-class resolver in the nwsapi internal logic.

[greglittlefield-wf]

I'm having a similar issue, in both 2.2.22 and 2.2.23, with the error

SyntaxError: 'input,,,,Ar1,,,A.MuiInputBase-input .MuiCheckbox-root' is not a valid selector

For reference, logging the value of selectors directly after this line:

nwsapi/src/nwsapi.js

Line 1589 in f1664d8

selectors = makeref(selectors, Snapshot.from);

yields #%3Ar1%3A.MuiInputBase-input .MuiCheckbox-root. The issue seems to be theid=":r1:" on the element.

However, if I make a the following change to this line to use an attribute selector:

-          (element.id ? '#' + escape(element.id) : '') +
+          (element.id ? `[id="${escape(element.id)}"]` : '') +

which results instead in input[id="%3Ar1%3A"].MuiInputBase-input .MuiCheckbox-root, then the selector works!

while now it is going to be implemented as a real pseudo-class resolver in the nwsapi internal logic

Do you think a workaround like this one could be put in place until that resolver is implemented?

[dperini]

@daelmaak
I already started to work on this.
It will take some time and a bit of help from you to debug and reviewing the needed changes.
Stay tuned.