move 3 rows to Earlier table

Author: mikehoffms

microsoft-edge/web-platform/site-impacting-changes.md

@@ -30,7 +30,6 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
 
 <!-- order of rows: newest version (such as "Future/TBD") at top, then greatest to smallest version # -->
 
-<!-- latest = 10 most recent versions (Stable channel); as of Feb. 10, 2025, latest Stable = 133, so the 10 most recent versions = 124 through 133 -->
 ##### [Latest versions](#tab/latest)
 
 | Change | Release | Description |
@@ -42,15 +41,15 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
 | WebGPU `maxInterStageShaderComponents` limit | v133 | The WebGPU `maxInterStageShaderComponents` limit is being removed.  See [Deprecate WebGPU limit maxInterStageShaderComponents](./release-notes/133.md#deprecate-webgpu-limit-maxinterstageshadercomponents). |
 | `<link rel=prefetch>` five-minute rule | v133 | Previously, when a resource was prefetched by using `<link rel=prefetch>`, its cache semantics (specifically, `max-age` and `no-cache`) were ignored for the first use within 5 minutes, to avoid refetching.  Now, this special case has been removed, and normal HTTP cache semantics are used. See [Remove `<link rel=prefetch>` five-minute rule](./release-notes/133.md#remove-link-relprefetch-five-minute-rule). |
 | Deprecate `textprediction` attribute | v133 | Removes support for the `textprediction` HTML attribute, which is a nonstandard attribute that's used to enable or disable the browser-based Text Prediction feature for long-form text inputs.  Instead, use the standardized `writingsuggestions` attribute, which functions similarly to `textprediction`, but also applies to other writing-assistance features that browsers may provide.  Sites that explicitly set `textprediction` to `true` or `false` can instead set `writingsuggestions` to the same value.  For more information, see [Writing suggestions](https://html.spec.whatwg.org/multipage/interaction.html#writing-suggestions) in the HTML specification. |
-| Removal of Token Binding support | v127, v130 | Token Binding uses cryptographic certificates on both ends of the TLS connection in an attempt to close the security gap of bearer tokens, which may be lost or stolen.  The enterprise policy [AllowTokenBindingsForUrls](/deployedge/microsoft-edge-policies#allowtokenbindingforurls) will no longer be supported, as of v127.  Support for the Token Binding protocol will be removed in v130. |
-| Removal of mutation events | v127 | Removes support for mutation events in Chromium. Use the [MutationObserver](https://developer.mozilla.org/docs/Web/API/MutationObserver) API instead.  See [Intent to Deprecate: Mutation Events](https://groups.google.com/a/chromium.org/g/blink-dev/c/qDsKRU-cQ_4/m/isA1mZ_aAAAJ). |
-| Removal of Web SQL | v124 | Fully removes Web SQL support. In prior releases, Web SQL support was disabled by default but could be re-enabled via the [WebSQLAccess policy](/deployedge/microsoft-edge-policies#websqlaccess). After this change, there is no longer any mechanism to enable Web SQL support. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see [Intent to Deprecate and Remove Web SQL](https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ). |
 
 
 ##### [Earlier versions](#tab/earlier)
 
 | Change | Release | Description |
 | --- | --- | --- |
+| Removal of Token Binding support | v127, v130 | Token Binding uses cryptographic certificates on both ends of the TLS connection in an attempt to close the security gap of bearer tokens, which may be lost or stolen.  The enterprise policy [AllowTokenBindingsForUrls](/deployedge/microsoft-edge-policies#allowtokenbindingforurls) will no longer be supported, as of v127.  Support for the Token Binding protocol will be removed in v130. |
+| Removal of mutation events | v127 | Removes support for mutation events in Chromium. Use the [MutationObserver](https://developer.mozilla.org/docs/Web/API/MutationObserver) API instead.  See [Intent to Deprecate: Mutation Events](https://groups.google.com/a/chromium.org/g/blink-dev/c/qDsKRU-cQ_4/m/isA1mZ_aAAAJ). |
+| Removal of Web SQL | v124 | Fully removes Web SQL support. In prior releases, Web SQL support was disabled by default but could be re-enabled via the [WebSQLAccess policy](/deployedge/microsoft-edge-policies#websqlaccess). After this change, there is no longer any mechanism to enable Web SQL support. This change is happening in the Chromium project, on which Microsoft Edge is based. For more information, see [Intent to Deprecate and Remove Web SQL](https://groups.google.com/a/chromium.org/g/blink-dev/c/fWYb6evVA-w/m/pziWcvboAgAJ). |
 | Added support for AVIF and AV1 file formats | v121 | Microsoft Edge now supports the AVIF and AV1 file formats, which offer better compression and higher quality images and videos.  Users can enjoy faster loading times and better quality media on websites. |
 | Removal of Native Client (NaCl) | v120 | To enhance web security and performance, Native Client (NaCl) is no longer supported for Microsoft Edge (along with other browsers).  NaCl was supported through v115.  In v116 through v119, NaCl was only usable by enabling an enterprise policy.  WebAssembly (Wasm) is recommended instead of NaCl; see [Run compiled code in an extension](../extensions-chromium/developer-guide/run-compiled-code.md). |
 | Ignore modifications to `document.domain` by default | v119 | The `document.domain` property historically could be set to relax the same-origin policy and allow subdomains from a site to interact.  This behavior will be disabled by default, such that setting the `document.domain` property will have no effect.  For more information and workarounds, see [Microsoft Edge will disable modifying document.domain](/deployedge/edge-learnmore-origin-keyed-agent-cluster). |