w3c
diff --git a/‎.github/workflows/auto-publish.yml‎
Lines changed: 1 addition & 3 deletions b/‎.github/workflows/auto-publish.yml‎
Lines changed: 1 addition & 3 deletions
diff --git a/‎index.html‎
Lines changed: 6 additions & 10 deletions b/‎index.html‎
Lines changed: 6 additions & 10 deletions
@@ -11,11 +11,9 @@ jobs:
     name: Validate and Publish
     runs-on: ubuntu-latest # only linux supported at present
     steps:
-      - uses: actions/checkout@v2
+      - uses: actions/checkout@v6
       - uses: w3c/spec-prod@v2
         with:
-          TOOLCHAIN: respec
-          VALIDATE_LINKS: true
           W3C_ECHIDNA_TOKEN: ${{ secrets.ECHIDNA_TOKEN }}
           W3C_WG_DECISION_URL: "https://lists.w3.org/Archives/Public/public-webapps/2014JulSep/0627.html"
           W3C_NOTIFICATIONS_CC: "${{ secrets.CC }}"
 
@@ -70,14 +70,14 @@
         github: "w3c/pointerlock",
         group: "webapps",
         xref: {
-                specs: ["uievents"],
+                specs: ["pointerevents"],
                 profile: "web-platform",
         },
       };
 
     </script>
   </head>
-  <body data-cite="uievents">
+  <body>
     <section id='abstract'>
       This specification defines an API that provides scripted access to raw
       mouse movement data while locking the target of mouse events to a single
@@ -169,7 +169,7 @@ <h3>
           reported in `screenX`, `screenY`). The [=pointer-lock target=]
           receives all relevant user generated {{MouseEvent}} events: namely,
           all user-generated `mousemove`, `mousedown`, `mouseup`, `click`,
-          `dblclick`, `auxclick`, and `wheel` [[ui-events]]. No other elements
+          `dblclick`, `auxclick`, and `wheel` [[POINTEREVENTS]]. No other elements
           receive these events while in [=pointer lock state=]. There will be
           no dispatching of events that require the concept of a mouse cursor:
           namely, `mouseenter`, `mouseleave`, `mouseover`, `mouseout`, `drag`,
@@ -599,8 +599,7 @@ <h2>
         </dd>
       </dl>
     </section>
-    <section data-dfn-for="MouseEvent" data-link-for="MouseEvent" data-cite=
-    "ui-events">
+    <section data-dfn-for="MouseEvent" data-link-for="MouseEvent">
       <h2>
         Extensions to the `MouseEvent` Interface
       </h2>
@@ -677,8 +676,7 @@ <h2>
         </dd>
       </dl>
     </section>
-    <section data-dfn-for="MouseEventInit" data-link-for="MouseEventInit"
-    data-cite="ui-events">
+    <section data-dfn-for="MouseEventInit" data-link-for="MouseEventInit">
       <h2>
         Extensions to the `MouseEventInit` Dictionary
       </h2>
@@ -1005,9 +1003,7 @@ <h2>
         <p>
           When the pointer is locked 'wheel' events should be sent to the
           [=pointer-lock target=] element just as 'mousemove' events are. There
-          is a naming conflict with .deltaX/Y/Z as defined in <a href=
-          "https://w3c.github.io/uievents/#events-wheelevents">DOM 3 'wheel'
-          event</a>.
+          is a naming conflict with {{WheelEvent/deltaX}}/{{WheelEvent/deltaY}}/{{WheelEvent/deltaZ}} [[POINTEREVENTS]].
         </p>
       </section>
       <section id="why-bundle">