tor-browser

commit 3969aaa14eddaccf4d9b969c0fa9fcdc6273b2e0
parent d2d007a2f0ee39d9ada4dedc536373036b6174b6
Author: Adam Vandolder <avandolder@mozilla.com>
Date:   Wed,  7 Jan 2026 15:29:27 +0000

Bug 2006468 - Use previously-determined triggering navigation type when deciding whether to reuse the navigation API key for a replace load. r=dom-core,farre

Differential Revision: https://phabricator.services.mozilla.com/D277946

Diffstat:
M
docshell/base/nsDocShell.cpp
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docshell/base/nsDocShell.cpp b/docshell/base/nsDocShell.cpp
@@ -8020,8 +8020,8 @@ nsresult nsDocShell::CreateDocumentViewer(const nsACString& aContentType,
   //         historyEntry's navigation API key to entryToReplace's
   //         navigation API key.
   bool isReplace =
-      mActiveEntry && mLoadingEntry && IsValidLoadType(mLoadType) &&
-      NavigationUtils::NavigationTypeFromLoadType(mLoadType)
+      mActiveEntry && mLoadingEntry &&
+      mLoadingEntry->mTriggeringNavigationType
           .map([](auto type) { return type == NavigationType::Replace; })
           .valueOr(false);
   if (isReplace) {