Diego Perini

@camchenry & @kmcgrady Closing this issue since it was completed and fixed by the merged pull request. Thank you for the help and the contributed fix.

@zuzusik I am trying to reconstruct the history of these additions to the list of pseudo-class selector considered in nwsapi. If I recall correctly the additions of these pseudo-class stems...

Obviously the code should check if the property yielding the true result does effectively allow for such a property and pseudo-class as we normally do for any other selectors considered...

@Fil ... yes the last commit brings a regression within the changes made to improve and further isolate HTML / XML / XHTML languages inside "nwsapi" so next cut release...

@miguel-leon yes it is related ... I almost fixed the spill. A mix up of wrong RegExps changes brought me here. The ability of parsing nested selectors compounds was not...

Wrong Regular expression caused this. Closing as completed. Reopen if necessary.

@miguel-leon regarding the resolver issue [h1 + h2 appears to break](https://github.com/dperini/nwsapi/issues/114#top) it was fixed. It had to do with wrong REs and other overlapping problems, not performing in the intended...

@chenshuai2144 Yes the selector you showed above is wrong. document.querySelector(':scope +.ant-select-item-option-selected:not(.ant-select-item-option-disabled))+.ant-select-item-option-selected:not(.ant-select-item-option-disabled'); the first :not() instance terminates with an extra parenthesis. This is the corrected broken down corrected version: document.querySelectorAll(':scope\ +.ant-select-item-option-selected\...

There is no issue here, it is just a wrong syntax as explained in my previous post and from @martijnpieters comment. It might have been confused with other errors during...

Should have been fixed by this commit fc7534b2f9d287f01d84376cc37b67f9cfc63c29 Please test ! And possibly report or reopen if needed.