Try adding this selector and check what happens:
youtube.com#$#:xpath(//div[@class='ytp-button ytp-paid-content-overlay-text']) { display: none; debug: true; }
We should handle naked :xpath selectors differently and pass it to document.evaluate right away: :xpath(//div[@class='ytp-button ytp-paid-content-overlay-text'])
The problem itself is caused by the way right-to-left matching works in Sizzle - for a selector like that it basically takes ALL DOM nodes and evaluates the pseudo-class for it.
Try adding this selector and check what happens:
youtube.com#$#:xpath(//div[@class='ytp-button ytp-paid-content-overlay-text']) { display: none; debug: true; }
We should handle naked
:xpath
selectors differently and pass it todocument.evaluate
right away::xpath(//div[@class='ytp-button ytp-paid-content-overlay-text'])
The problem itself is caused by the way right-to-left matching works in Sizzle - for a selector like that it basically takes ALL DOM nodes and evaluates the pseudo-class for it.