Needs some more investigation because some subtests in resolver-callback-interface.html do expect a type error to be thrown.

Chrome also fails those two remaining tests: https://wpt.fyi/results/domxpath/resolver-callback-interface.html?label=master&label=experimental&product=servo&product=firefox&product=chrome&aligned&q=domxpath

Firefox somehow throws both a type error and a namespace DOMException in the same document.evaluate call, which matches the test expectations. I wasn't able to replicate that, but if chrome isn't doing it then there's likely no point...