New issue
Advanced search Search tips

Issue 894356 link

Starred by 1 user
Status: WontFix
Owner:
droger@chromium.org
Closed: Oct 11
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Sync get automatically paused when clicked on delete button in 'Edit this cookie' extension.

Reported by shruti.j...@etouch.net, Oct 11 
Chrome Version: 71.0.3576.0 (Official Build)  Revision	bc9a92a53c6a87c2857f18371e9f32b1f0f895cb-refs/branch-heads/3576@{#1}(64-bit)
OS : Windows(7, 8, 8.1 ,10) Mac(10.13.1,10.13.6, 10.14.1), Linux(14.04 LTS)

Pre-condition:Sign in to chrome with valid credentials.

Test URL:https://chrome.google.com/webstore/detail/editthiscookie/fngmhnnpilhplaeedifhccceomclgfbg


Steps to reproduce :
1.Launch chrome and Navigate to above URl and download the extension.
2.Navigate to Eg..hangouts.google.com and click on 'edit cookie extension'
3.Now Click on delete button and observe.

Actual Result :Sync get automatically paused when clicked on delete button.
Expected Result :Sync should not get automatically paused when clicked on delete button.

This is a regression issue broken in ‘M-71’ and will soon inform the bisect info:
Good Build :71.0.3568.0 
Bad Build : 71.0.3569.0 

Kindly refer the attached screen-cast.

Thank you..!
Expected_Result.mp4
794 KB View Download
Actual_result.mp4
650 KB View Download

Comment 1 by shruti.j...@etouch.net, Oct 11

Labels: RegressedIn-71 Target-71 FoundIn-71 hasbisect
Owner: droger@chromium.org
Status: Assigned (was: Unconfirmed)
Udpate:
Bisect info:

Change log:

https://chromium.googlesource.com/chromium/src/+log/71.0.3568.0..71.0.3569.0?pretty=fuller&n=10000

Suspect:https://chromium.googlesource.com/chromium/src/+/c6ecc920322d2df4dc1adb73734173bd983c45bc

@David Roger:Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Note:
1.Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message.
2.Tried on other machines but still getting the same error again.
3.In 'Chromium bisect' Sign-in chrome is not available,Hence providing suspect Manually from Change Log.
4.Issue is also seen on latest canary #71.0.3577.0 and Dev #71.0.3573.0.


Thank you..!

Comment 2 by droger@chromium.org, Oct 11

Status: WontFix (was: Assigned)
Thanks for the report.

My CL indeed changed this behavior, and it was done on purpose.

This is implementing what is described here, at the bottom:
https://www.blog.google/products/chrome/product-updates-based-your-feedback/

"We’re also going to change the way we handle the clearing of auth cookies. In the current version of Chrome, we keep the Google auth cookies to allow you to stay signed in after cookies are cleared. We will change this behavior that so all cookies are deleted and you will be signed out."


I believe this is WAI, unless I am missing something. Closing this, please reopen if you think there is a problem.
►

Sign in to add a comment