New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 734989 link

Starred by 7 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression


Participants' hotlists:
Hotlist-1


Sign in to add a comment

WebStorage.deleteOrigin(origin) not working on Android O Developer Preview 3 for some origins like www.facebook.com

Reported by sanketga...@gmail.com, Jun 20 2017

Issue description

Steps to reproduce the problem:
1. Call WebStorage.getInstance().deleteOrigin(origin)
2. After some time call WebStorage.getInstance().getOrigins()

What is the expected behavior?
WebStorage.getInstance().getOrigins() should return origin with usage as 0

What went wrong?
WebStorage.getInstance().getOrigins() still returning the origin with previous usage. Works for some website(For e.g. www.gmail.com) but doesn't work for others(For e.g. www.facebook.com)

Did this work before? Yes Nougat

Chrome version: 58.0.3029.121  Channel: stable
OS Version: 8.0
Flash Version: Shockwave Flash 26.0 r0

It used to work fine till Android N, not working in Android O Developer Preview 3
 
Been a week, please get back on this so that it's fixed in Android O main release atleast
Cc: sandeepkumars@chromium.org
Labels: Needs-triage-Mobile Triaged-Mobile Needs-Feedback
@sanketgarg1992: Thanks for the report!!

Could you please let us know are you still able to reproduce the issue in latest Chrome builds?

Thanks!!

This is still happening for twitter.com
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 21 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Could you please upgrade your Chrome to the latest stable #62.0.3202.84 and check if you still face the issue? If so attach a sample file and a screencast to check the issue from our end.

Thanks!!
Components: Blink>Storage
It is resolved for twitter, but happening for certain other sites like www.google.com
Project Member

Comment 8 by sheriffbot@chromium.org, Jan 23 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 9 by jsb...@chromium.org, Jan 30 2018

Components: Mobile>WebView
Labels: Needs-Feedback
Is the problem that the origin is still present? Or is the data not being erased?

This might be a dupe of 527666 i.e. working as intended
It's a problem of data not being erased. I have handled 527666 separately in my application and this issue occurs only on Android O
Project Member

Comment 11 by sheriffbot@chromium.org, Jan 31 2018

Cc: jsb...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "jsbell@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Arch-x86_64 -Needs-triage-Mobile Needs-Feedback
there is nothing in this code that's specific to a particular domain. ie there is no reason this works for twitter.com but not facebook.com. it should be either broken for all domains, or working for all domains.

so this leads me to think there is something else going on here. eg did you load facebook again between clearing data and checking again. how did you check data is not erased?

this would be easier if you can attach an apk to demonstrate the problem
Status: WontFix (was: Unconfirmed)
There is no feedback since the past 1 month, closing for now. Feel free to reopen if needed.

Sign in to add a comment