Bug 1627420 - Ensure we clear userTyped properties when doing a process flip. r=mattwoodrow
This effectively also undoes the change introduced in 3166149f37f1 (bug 1615302), and makes it so that instead of ignoring the userTyped values, we clear them out in the parent when doing a process flip before sending them down to the new child process. Differential Revision: https://phabricator.services.mozilla.com/D69862
This commit is contained in:
@@ -305,17 +305,11 @@ ContentRestoreInternal.prototype = {
|
||||
csp,
|
||||
};
|
||||
webNavigation.loadURI(loadArguments.uri, loadURIOptions);
|
||||
} else if (
|
||||
tabData.userTypedValue &&
|
||||
tabData.userTypedClear &&
|
||||
!isRemotenessUpdate
|
||||
) {
|
||||
} else if (tabData.userTypedValue && tabData.userTypedClear) {
|
||||
// If the user typed a URL into the URL bar and hit enter right before
|
||||
// we crashed, we want to start loading that page again. A non-zero
|
||||
// userTypedClear value means that the load had started.
|
||||
// Load userTypedValue and fix up the URL if it's partial/broken.
|
||||
// Remoteness updates are not crashes, so we use the provided URL, not
|
||||
// the user typed one.
|
||||
let loadURIOptions = {
|
||||
triggeringPrincipal: Services.scriptSecurityManager.getSystemPrincipal(),
|
||||
loadFlags: Ci.nsIWebNavigation.LOAD_FLAGS_ALLOW_THIRD_PARTY_FIXUP,
|
||||
|
||||
Reference in New Issue
Block a user