[gravitypdf-bot]

remove($selector) and replaceAll($selector, $document) were the last callers of the legacy QueryPath\CSS\QueryPathEventHandler engine, which disagrees with find() in three ways:

$xml = '<?xml version="1.0"?><root><p><i>a</i><b>x</b></p><p><i>b</i></p><i>c</i></root>';
qp($xml, 'p')->remove('p')->count();   // was 2 (the <p>s themselves), now 0, as detach('p') and find('p')

$xml = '<?xml version="1.0"?><ul><li id="a"/><li id="b" class="x"/><li id="c"/></ul>';
qp($xml)->remove('li:matches(.x)');    // threw "Unknown Pseudo-Class: matches", now removes b
qp($xml)->remove('li:not(:first)');    // removed nothing, now removes b, c
qp($xml)->remove('li:not(:odd)');      // removed a, b, c, now removes a, c

Changes

• remove($selector) runs DOMTraverser over the match set. That is what find() does, but find() itself isn't called, because inst() deep-clones the match set. remove() and detach($selector) now agree on every selector.
• replaceAll($selector, $document) runs DOMTraverser seeded with $document->documentElement, which is how qp($document) seeds it. The selector still searches the whole target document, document element included (the Make find() search descendants only, as jQuery does #73 exception), and the current match set still only supplies the replacement.
• QueryPathEventHandler is left in place and unchanged apart from a @deprecated docblock pointing at DOMTraverser. No runtime notice. Docblocks that named it as the engine behind these methods are updated.
• CHANGELOG: new Behaviour change entry. I also corrected two Unreleased entries that said remove()/replaceAll() still use the legacy engine; one of them also claimed the legacy engine agreed on all positional pseudo-classes, which isn't true inside :not() (remove('li:not(:first)') and other positional :not() arguments are evaluated per element in the legacy engine #124).

Behaviour change

remove($selector) now searches the descendants of the match set only, so a selector that matched the nodes in hand no longer removes them. Use filter($selector)->remove() to get the old result. Selectors that used to throw (:matches()) now work.

Tests

• New tests/Issues/Issue126Test.php: the remove() and replaceAll() throw "Unknown Pseudo-Class: matches" for :matches() #123 and remove('li:not(:first)') and other positional :not() arguments are evaluated per element in the legacy engine #124 tables run through remove() and replaceAll() for qp(), htmlqp() and html5qp(), plus the remove() and replaceAll() still match the nodes in hand, unlike find() #126 examples, the document-element case for both methods, and a check that replaceAll() searches the whole document. 31 of its 39 tests fail on main.
• DOMQueryTest::testDetachWithSelectorAgreesWithRemove now includes 'p' and '*' in the agreement loop. The pinning assertions are gone.
• Issue66Test::testRemoveAgreesWithFind no longer sorts before comparing, so it checks order as well.
• None of the existing remove()/replaceAll() expectations had to change.

:is() is not added here. To work with positional arguments it also needs adding to Util::SELECTOR_ARGUMENT_PSEUDO_CLASSES, so it's left for a follow-up.

Fixes #123
Fixes #124
Fixes #126

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.16%. Comparing base (6ae6acf) to head (ba44e04).
⚠️ Report is 14 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #127      +/-   ##
============================================
+ Coverage     90.69%   91.16%   +0.47%     
- Complexity     1424     1460      +36     
============================================
  Files            25       26       +1     
  Lines          3170     3227      +57     
============================================
+ Hits           2875     2942      +67     
+ Misses          295      285      -10     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.