Prerequisites

• I verified that this is not a filter issue
  • Filter issues MUST be reported at filter issue tracker
• This is not a support issue or a question
  • Support issues and questions are handled at /r/uBlockOrigin
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue
  • Your issue may already be reported.
• I tried to reproduce the issue when...
  • uBlock Origin is the only extension
  • uBlock Origin with default lists/settings
  • using a new, unmodified browser profile
• I am running the latest version of uBlock Origin
• I checked the documentation to understand that the issue I report is not a normal behavior

Description

Block someting with xpath and use comma after xpath:

github.com###issue-418448972:xpath(..), blablacar

Try find logger and you found:

A specific URL where the issue occurs

#453

Steps to Reproduce

1. open this issue Properly report :spath operator of procedural cosmetic filters in logger #453
2. create filter by element picker ##.js-comment-body:xpath(..), blablacar
3. refresh page and possible in ubo logger you found ##.js-comment-body:xpath(..):spath(, blablacar)

Expected behavior:

mark filter as invalid?

or add works exception + marks spath as valid operator:

#@##issue-418448972:xpath(..):spath(, li)

Actual behavior:

other selector moved to :spath(...) to not discard filter? and expception without remove spath does not work.

Your environment

• uBlock Origin version: Windows 7
• Browser Name and version: Firefox 65
• Operating System and version: uBO 1.18.5rc3