From c43aff82f59204d9fe9f8330a3af1da4efa3a9df Mon Sep 17 00:00:00 2001
From: Domenic Denicola <d@domenic.me>
Date: Wed, 5 Jun 2024 15:11:46 +0900
Subject: [PATCH] Don't set hashChange to true for classic history API navigate
 events

Closes #10389.
---
 source | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/source b/source
index c38363d0918..809aeb97590 100644
--- a/source
+++ b/source
@@ -94761,6 +94761,10 @@ interface <dfn interface>NavigationDestination</dfn> {
     <p>If all of the following are true:</p>
 
     <ul>
+     <li><p><var>event</var>'s <span
+     data-x="concept-NavigateEvent-classic-history-API-state">classic history API state</span> is
+     null;</p></li>
+
      <li><p><var>destination</var>'s <span data-x="concept-NavigationDestination-sameDocument">is
      same document</span> is true;</p></li>
 
@@ -94776,6 +94780,11 @@ interface <dfn interface>NavigationDestination</dfn> {
     <p>then initialize <var>event</var>'s <code
     data-x="dom-NavigateEvent-hashChange">hashChange</code> to true. Otherwise, initialize it to
     false.</p>
+
+    <p class="note">The first condition here means that <code
+    data-x="dom-NavigateEvent-hashChange">hashChange</code> will be true for <span
+    data-x="navigate-fragid">fragment navigations</span>, but false for cases like <code
+    data-x="">history.pushState(undefined, "", "#fragment")</code>.</p>
    </li>
 
    <li><p>If <var>userInvolvement</var> is not "<code data-x="uni-none">none</code>", then