From 9afc0d64707caa64ae750dc8117cbb2c4194a52a Mon Sep 17 00:00:00 2001
From: James Graham
Date: Wed, 13 Oct 2021 16:22:57 +0100
Subject: [PATCH] Ensure we do a fragment navigated callback for any case where
there will be no load event.
In particular if webdriver initiates a navigation to the current URL and it includes a fragment, this seems to
be required to ensure the navigation completes on the WebDriver side.
---
source | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/source b/source
index 8957cfb49a3..16fa7b861cf 100644
--- a/source
+++ b/source
@@ -84930,7 +84930,7 @@ interface History {
data-x="navigation-status-status">status is "canceled
", and url is source browsing context's active
- document's URL
+ document's URLurl.
Return.
@@ -88584,6 +88584,23 @@ new PaymentRequest(…); // Allowed to use
data-x="navigation-status-complete">complete".
+ If stateChanged is false, hashChanged is false and
+ entry's document equals the
+ current entry's document, then:
+
+
+
+
+ Invoke WebDriver BiDi fragment navigated with newDocument's
+ browsing context and a new WebDriver
+ BiDi navigation status whose id is
+ navigationId, url is
+ resource's URL, and status is "complete
".
+
+