Issue metadata
Sign in to add a comment
|
Chrome shouldn't attempt to restore tabs if the user explicitly closed the browser.
Reported by
nielsen....@gmail.com,
Sep 17 2016
|
||||||||||||||||||||||||
Issue descriptionExample URL: Applies to all URLS Steps to reproduce the problem: 1. Visit a page. 2. Close the chrome browser by pressing the "apps" key on your android device, and then either swipe chrome browser to the right/left, or press the button "Close all". 3: Start chrome again What is the expected behavior? Chrome should at a user-initiated exit, ONLY load the configured start page. It should **NOT** attempt to restore the previous session. If its impossible to detect if a user-initiated exit was performed from the Android app manager, then Chrome should never attempt to restore tabs that have an URL that contains a ?. (eg, contains GET parameters). Eg, such tabs is lost forever. This is preferable to be made user-configurable from settings. Like: "Restore sessions?" () Never () Only static pages (that does not contain ?) () Always What went wrong? The problem is that Chrome restores the session even at a user-initiated exit, causing the browser to fire out requests that the user did not intend. Think like credit card orders and such, that get processed twice, or sensitive actions like deleting things and such. If the user explicitly has selected to close the browser, the session should be restarted from a fresh one. Did this work before? No Chrome version: 799386cbf7c1cbf70c12c0e593b2b2e23e39ba30-refs/branch-heads/2743_91@{#19} Channel: stable OS Version: 6.0.1 Flash Version: N/A Sending out requests twice, for example a GET request to like http://www.example.org/processOrder.php?orderID=9843759375 can cause unintended side-effects like dual charges for old orders.
,
Sep 21 2016
If this is implemented, there is a risk that a whole host of users are annoyed when they start back up after updating because the default behaviour of the browser is changed. For what it's worth, I disagree with the request and believe that, if implemented, it should be disabled by default. There are plenty of examples where urls contain querystring params but it would be desirable to restore those tabs (crbug.com being one such example!). I do believe that there should be the ability to choose what to do on start-up, similar to desktop. Namely: () Open the New Tab page () Continue where you left off () Open a specific page or set of pages (with option to set)
,
Sep 21 2016
Yeah, I also agree that it should be a setting. Good idea. Got so put off when I saw that charge on my account statement and it turned out to be a purchased download that was processed twice due to this restoring of tabs. (it restored a "Thank you for your order, here is your downloads" tab with a url like as I shown, with like orderID=xxxxxx in the end causing the order to be performed again). But anyways, it was just 1$ so it don't matter. But what would happen if that was a 500$ order? The thing is that if I close the browser manually, I close it because im finished with the session. I agree that restoring sessions is a good idea, but if that requires sending out requests, it should be more careful IMHO. Maybe this issue could be solving with some cache system, so even if it restores the session completely, it will always ensure it restores 100% from cache and never sends out network traffic as a result of restoration.
,
Dec 16 2016
,
Dec 16 2016
,
Mar 24 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, Sep 20 2016