Failure of Chrome to delete user history in Android
Reported by
scorpion...@gmail.com,
May 5 2016
|
||
Issue descriptionThis template is ONLY for reporting privacy issues. Please use a different template for other types of bug reports. Please see http://www.chromium.org/Home/chromium-privacy for further information. PRIVACY ISSUE So couple of days ago I noticed a bug in Chrome. Whenever I go to history menu from the three dot menu and then I select clear history and further select from beginning of time and then press clear it fails to do it. I have tried this on multiple android devices yielding same results. VERSION: Chrome Version: [50.0.2661. 89] + [stable] Operating System: [Android 5.1.1 ] Device: Motorola Moto E 2nd Gen XT1506 REPRODUCTION STEPS: I usually clear my browsing history for my own personal reasons. And that's where I noticed it. People must have been clearing history and are assured when it's finished but I bet they don't go again to check if it's cleaned or not. Video: https://drive.google.com/file/d/0B2f71PeCk0I5SXZhM3Q1TVZKLVE/view?usp=drivesdk
,
May 19 2016
Thanks for the report, scorpion.ashutosh29! I watched the video closely, and it's not the same I was looking into. In this case, the problem is not on the history page. The data are actually not deleted, as is indicated by: - the counter showing "76 items" after returning to the Clear Browsing Data dialog - the fact that the history page did not reload when the dialog was first closed, meaning it did not register a deletion I believe that the deletion, in this case the SQL DELETE query to the local history database, failed. This is silent; BrowsingDataRemover, let alone the UI, are not informed of errors. While I cannot investigate from the video why the query failed, I think we should improve BrowsingDataRemover to handle failures and communicate them to the UI, so the user at least isn't led to believe that the deletion succeeded when it didn't. Before we come up with a UX design though, this needs a lot of backend work at first. |
||
►
Sign in to add a comment |
||
Comment 1 by battre@chromium.org
, May 6 2016