Evidencecheerio-1101

find() convert `xlink:href` to `href`

cheerio#1101, at commit 74be271. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

NO_FAILURE_OBSERVED

executed against the upstream checkout.

Outcome
INCONCLUSIVE
Wall time
88.2s
Checks
3 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Issue
#1101
Pinned commit
74be27115020fca7c08a1c177d3b6fc487b9194b

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

cheerio#1101 · as filedcommit 74be271

find() convert `xlink:href` to `href`


`cheerio@^1.0.0-rc.2` automatically converts `xlink:href` to `href` when using `find()`.

```js
cheerio.load('')('<span><svg ><use xlink:href="#1" /></svg></span>').find('use').prop('xlink:href') //undefined
cheerio.load('')('<span><svg ><use xlink:href="#1" /></svg></span>').find('use').prop('href') //#1
```

Since, Safari doesn't support `href` without the "xlink" prefix in svg yet. Maybe, leave `xlink:href` as it was in `cheerio@^0.22.0` is better?
Issue
#1101
Commit
74be27115020fca7c08a1c177d3b6fc487b9194b
Why this commit
The first parent of the fix commit ca6963c09a38eaf67fbe551634fdbbc6984d3da8, which GitHub binds to this issue via CROSS_REFERENCED_PR. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
cheerio.load('')('<span><svg ><use xlink:href="#1" /></svg></span>').find('use').prop('xlink:href') does not produce undefined; the fix makes it do so.
Expression
cheerio.load('')('<span><svg ><use xlink:href="#1" /></svg></span>').find('use').prop('xlink:href')
Where that came from
Read mechanically from the report's fenced code, SAME_LINE form: `cheerio.load('')('<span><svg ><use xlink:href="#1" /></svg></span>').find('use').prop('xlink:href') //undefined`.

03What happened

No failure was captured.

Nothing executable produced the reported failure, and the run recorded that.

bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

Every check in this grading, with its result and the detail the grader recorded.
CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedfailThe reproduction ran and demonstrated no failure.
right-failurefailExpected `cheerio.load('')('<span><svg ><use xlink:href="#1" /></svg></span>').find('use').prop('xlink:href')` not producing undefined.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out 74be271, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/cheeriojs/cheerio
git checkout 74be27115020fca7c08a1c177d3b6fc487b9194b
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color