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

Issue 739274 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug

Blocked on:
issue 656758



Sign in to add a comment

Regression: Added exception is not deleted after using clear and exit option in settings

Project Member Reported by sc00335...@techmahindra.com, Jul 5 2017

Issue description

Chrome Version: 61.0.3149.0 dev
OS: Ubuntu 14.04,Windows

What steps will reproduce the problem?
1. Launch chrome and Go to chrome://flags and enable Site settings with All sites and Site details.
2. Navigate to chrome://md-settings/content/cookies and Add a site in block section.
3. Go to Site details and click on clear and reset button and observe.[Please refer video]


Expected:Site should get deleted on using clear and exit option
Actual:Site is not deleted,it is still seen under block section.

This is a regression issue broken in M61.

Good Build:61.0.3145.0
Bad Build: 61.0.3146.0
 
Expected_all sites.ogv
955 KB View Download
Actual_all sites.ogv
1.2 MB View Download

Comment 1 by ajha@chromium.org, Jul 5 2017

Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
Issue is seen on the latest Mac canary(61.0.3148.0) as well.
Labels: -Needs-Bisect hasbisect-per-revision
Owner: patricia...@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,

Good build: 61.0.3145.0(Revision:483574).
Bad build:  61.0.3146.0(Revision:483866).

You are probably looking for a change made after 483613 (known good), but no later than 483614 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/c0f1967e5ded7b35fb1a065f97e94502ad370843..f3b6e00fe2826406218b15bd2f317cfebe835696

From the CL above, assigning the issue to the concern owner

@patricialor: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url: https://codereview.chromium.org/2936003003

Thanks!!
Cc: raymes@chromium.org
Labels: -Pri-1 -M-61 OS-Chrome Pri-2
Thanks for the report and bisect! Yes, I think this is my fault.

+raymes - do you think we should be linking to Site Details from here, since we don't want cookies in there at all? (I already have https://chromium-review.googlesource.com/c/563137 in progress to remove them.)

Demoting priority since this bug is behind a flag, plus m61 has passed feature freeze.

Comment 4 by raymes@chromium.org, Jul 10 2017

Labels: -Type-Bug-Regression Type-Bug
Good catch and good question. I'm not sure whether we want to link from content settings directly into site details. If we do, we would only want to do it for origins and not general patterns. My feeling would be not to do it for the first cut and to think it through more later.
Blockedon: 656758
Oops, I missed your reply, thanks. I'll leave this bug for later then as turning on #enable-site-details won't link Site Details from content settings. 

Sign in to add a comment