Diego Perini

Commit 1a3a5c5989dc0e7943b68333c539d57e3454ab14 (0094625e362d39d261e0a2abac3a3111d370df9c was a wrong commit reference, sorry) is an attempt at fixing the handling of mangled selectors as argument to the :has() pseudo-class. Please test & report possible...

@cpmotion thank you for reviewing ongoing changes ... The commit reference in my previous message above is wrong, also the description in commit 0094625 is correct. It should have referenced...

@KindaOK thank you so much for the contribution. I confirm that your code is almost complete regarding the minimal :has() support (for WPT basic and invalidation tests). I am trying...

@KindaOK here is the state of my tests proceedings using your suggestions: 

@KindaOK what you suggested seems to be adequate for the task. So let's get a reference to the current :scope element using "querySelector" via the existing _makeref()_ function and without...

@KindaOK great help and info above. Thank you for your time. I also believe the arguments to :has() would need to be treated as specific cases, differently by different combinators....

@KindaOK .... I just realized that yesterday you found out about `Snapshot.from`. >>This change uses the Snapshot.from property since that appears to be the context for a given selector. this...

All reported issues having the error similar to "is not a valid selectors" had a common cause. The nesting Regular Expression in the recently added :has() pseudo-class resolver was wrong....

Thank you @domenic ... I am working on the bugs/fixes you listed. Especially trying to resolve the **is not a valid selector** regression.

@alopix thank you for the help. Yes it is the same bug affecting everybody. Still need a couple of days working on it and testing.