Re: [pointerevents] Fix typo in pointerup event definition markup (#651)

My friend Claude says:
```
The ReSpec failure on #651 isn't caused by the change. The site ReSpec downloads MDN data from has moved, so this error currently happens on every build of the
 spec, including unmodified gh-pages.

 What's going on:
 - The error: the only ReSpec error in that job is Could not find MDN data associated with key "pointerevents". The build runs ReSpec with -e, so any error
   fails it.
 - Cause: the w3c/mdn-spec-links repo was transferred to speced/mdn-spec-links around Sep 19–24. GitHub doesn't redirect Pages sites when a repo moves, so every
   file under https://w3c.github.io/mdn-spec-links/ now returns 404. The data is now at https://speced.github.io/mdn-spec-links/.
 - Why it broke now: ReSpec still hardcodes the old URL, in the latest release (37.4.0) and on main. The last passing pointerevents run (Sep 8) was before the
   move, not a different ReSpec behaviour.
 - Scope: every ReSpec spec that pulls in MDN data is affected, not just pointerevents. I couldn't find an existing ReSpec issue or PR for it.
 - The hint is misleading: the error suggests the mdn key is wrong, but "pointerevents" is correct.

 Two ways to fix it:
 1. Fix ReSpec (the real fix): change one line in speced/respec's src/core/mdn-annotation.js to BASE_JSON_PATH = "https://speced.github.io/mdn-spec-links/".
    Once that's released, the build picks up the new ReSpec automatically, so re-running #651's checks should pass with no change to pointerevents.
 2. Stopgap in pointerevents: change the config to mdn: { key: "pointerevents", baseJsonPath: "https://speced.github.io/mdn-spec-links/" }. I rendered this with
    spec-generator: the error goes away (1 → 0) and the MDN boxes render again (5 boxes, 31 MDN links; with the old URL there are none). This should be its own
    PR rather than going into the typo fix.

```


-- 
GitHub Notification of comment by yoavweiss
Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/651#issuecomment-5928544757 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 1 October 2026 09:22:53 UTC