From fd10ee105af74c5559c0021c2ada0997e943ac87 Mon Sep 17 00:00:00 2001 From: JustOff Date: Sat, 28 Apr 2018 14:41:28 +0300 Subject: Use `urlbarChangeTracker` instead of `userTypedClear` to track address bar changes --- application/palemoon/components/sessionstore/SessionStore.jsm | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'application/palemoon/components/sessionstore/SessionStore.jsm') diff --git a/application/palemoon/components/sessionstore/SessionStore.jsm b/application/palemoon/components/sessionstore/SessionStore.jsm index f7c495be8..b8d126e21 100644 --- a/application/palemoon/components/sessionstore/SessionStore.jsm +++ b/application/palemoon/components/sessionstore/SessionStore.jsm @@ -1951,7 +1951,13 @@ var SessionStoreInternal = { // userTypedValue. if (browser.userTypedValue) { tabData.userTypedValue = browser.userTypedValue; - tabData.userTypedClear = browser.userTypedClear; + // We always used to keep track of the loading state as an integer, where + // '0' indicated the user had typed since the last load (or no load was + // ongoing), and any positive value indicated we had started a load since + // the last time the user typed in the URL bar. Mimic this to keep the + // session store representation in sync, even though we now represent this + // more explicitly: + tabData.userTypedClear = browser.didStartLoadSinceLastUserTyping() ? 1 : 0; } else { delete tabData.userTypedValue; delete tabData.userTypedClear; -- cgit v1.2.3